Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
<p><br>
On Apr 12, 2012 4:57 PM, "Konstantin" <<a href="mailto:konstantin@...">konstantin@...</a>> wrote:<br>
><br>
> Hello,<br>
><br>
> With the help of Nikita, I've figured out how to get rid of<br>
> "xvda: unknown partition table"<br>
><br>
> I have to use /dev/xvda1 not the /dev/xvda<br>
><br>
> -------------------------------------<br>
> disk = ['phy:/dev/vg01/vm0,xvda,w']<br>
> root = '/dev/xvda ro'<br>
> -------------------------------------<br>
><br>
> changed to:<br>
><br>
> -------------------------------------<br>
> disk = ['phy:/dev/vg01/vm0,xvda1,w']<br>
> root = '/dev/xvda1 ro'<br>
> -------------------------------------<br>
><br>
> Anyway booting freezes. Once I've saw:<br>
><br>
> -------------------------------------<br>
> TCP cubic registered<br>
> XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...<br>
> XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 1)<br>
> XENBUS: Timeout connecting to device: device/vif/0 (local state 1, remote state 1)<br>
> VFS: Cannot open root device "xvda1" or unknown-block(0,0)<br>
> Please append a correct "root=" boot option; here are the available partitions:<br>
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)<br>
> Pid: 1, comm: swapper/0 Not tainted 3.2.12-gentoo #2<br>
> Call Trace:<br>
> [<ffffffff81318ebd>] ? panic+0x92/0x199<br>
> [<ffffffff81319004>] ? printk+0x40/0x4c<br>
> [<ffffffff814f4e2e>] ? mount_block_root+0x238/0x24f<br>
> [<ffffffff814f4fc0>] ? prepare_namespace+0x12c/0x156<br>
> [<ffffffff814f4b3e>] ? kernel_init+0x10a/0x113<br>
> [<ffffffff8131d074>] ? kernel_thread_helper+0x4/0x10<br>
> [<ffffffff8131bd33>] ? int_ret_from_sys_call+0x7/0x1b<br>
> [<ffffffff8131b43c>] ? retint_restore_args+0x5/0x6<br>
> [<ffffffff8131d070>] ? gs_change+0x13/0x13<br>
> -------------------------------------<br>
><br>
> So I guess may be it's related to some DomU kernel configuration<br>
> problem? I've attached it to this letter.<br>
><br>
> test # cat .config | grep XEN<br>
> CONFIG_XEN=y<br>
> CONFIG_XEN_DOM0=y<br>
> CONFIG_XEN_PRIVILEGED_GUEST=y<br>
> CONFIG_XEN_PVHVM=y<br>
> CONFIG_XEN_MAX_DOMAIN_MEMORY=128<br>
> CONFIG_XEN_SAVE_RESTORE=y<br>
> # CONFIG_XEN_DEBUG_FS is not set<br>
> CONFIG_PCI_XEN=y<br>
> CONFIG_XEN_PCIDEV_FRONTEND=y<br>
> CONFIG_XEN_BLKDEV_FRONTEND=y<br>
> CONFIG_NETXEN_NIC=m<br>
> CONFIG_XEN_NETDEV_FRONTEND=y<br>
> CONFIG_HVC_XEN=y<br>
> CONFIG_XEN_BALLOON=y<br>
> CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y<br>
> CONFIG_XEN_SCRUB_PAGES=y<br>
> CONFIG_XEN_DEV_EVTCHN=y<br>
> # CONFIG_XEN_BACKEND is not set<br>
> CONFIG_XENFS=y<br>
> CONFIG_XEN_COMPAT_XENFS=y<br>
> CONFIG_XEN_SYS_HYPERVISOR=y<br>
> CONFIG_XEN_XENBUS_FRONTEND=y<br>
> CONFIG_XEN_GNTDEV=m<br>
> CONFIG_XEN_GRANT_DEV_ALLOC=m<br>
> CONFIG_SWIOTLB_XEN=y<br>
><br>
> --<br>
> Konstantin</p>
<p>Have you tried:</p>
<p> root = '/dev/xvda1'</p>
<p>That is, without 'ro'? </p>
<p>Rgds, <br>
</p>
|
|
