| 1 |
Should be googled easily: you need to modify your inittab adding |
| 2 |
entries for xen virtual console |
| 3 |
|
| 4 |
hvc0:2345:respawn:/sbin/getty 38400 hvc0 |
| 5 |
xvc0:2345:respawn:/sbin/getty 38400 xvc0 |
| 6 |
|
| 7 |
On Thu, Apr 12, 2012 at 1:55 PM, Konstantin <konstantin@××××××××.com> wrote: |
| 8 |
> Hello, |
| 9 |
> |
| 10 |
> With the help of Nikita, I've figured out how to get rid of |
| 11 |
> "xvda: unknown partition table" |
| 12 |
> |
| 13 |
> I have to use /dev/xvda1 not the /dev/xvda |
| 14 |
> |
| 15 |
> ------------------------------------- |
| 16 |
> disk = ['phy:/dev/vg01/vm0,xvda,w'] |
| 17 |
> root = '/dev/xvda ro' |
| 18 |
> ------------------------------------- |
| 19 |
> |
| 20 |
> changed to: |
| 21 |
> |
| 22 |
> ------------------------------------- |
| 23 |
> disk = ['phy:/dev/vg01/vm0,xvda1,w'] |
| 24 |
> root = '/dev/xvda1 ro' |
| 25 |
> ------------------------------------- |
| 26 |
> |
| 27 |
> Anyway booting freezes. Once I've saw: |
| 28 |
> |
| 29 |
> ------------------------------------- |
| 30 |
> TCP cubic registered |
| 31 |
> 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... |
| 32 |
> XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 1) |
| 33 |
> XENBUS: Timeout connecting to device: device/vif/0 (local state 1, remote state 1) |
| 34 |
> VFS: Cannot open root device "xvda1" or unknown-block(0,0) |
| 35 |
> Please append a correct "root=" boot option; here are the available partitions: |
| 36 |
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) |
| 37 |
> Pid: 1, comm: swapper/0 Not tainted 3.2.12-gentoo #2 |
| 38 |
> Call Trace: |
| 39 |
> [<ffffffff81318ebd>] ? panic+0x92/0x199 |
| 40 |
> [<ffffffff81319004>] ? printk+0x40/0x4c |
| 41 |
> [<ffffffff814f4e2e>] ? mount_block_root+0x238/0x24f |
| 42 |
> [<ffffffff814f4fc0>] ? prepare_namespace+0x12c/0x156 |
| 43 |
> [<ffffffff814f4b3e>] ? kernel_init+0x10a/0x113 |
| 44 |
> [<ffffffff8131d074>] ? kernel_thread_helper+0x4/0x10 |
| 45 |
> [<ffffffff8131bd33>] ? int_ret_from_sys_call+0x7/0x1b |
| 46 |
> [<ffffffff8131b43c>] ? retint_restore_args+0x5/0x6 |
| 47 |
> [<ffffffff8131d070>] ? gs_change+0x13/0x13 |
| 48 |
> ------------------------------------- |
| 49 |
> |
| 50 |
> So I guess may be it's related to some DomU kernel configuration |
| 51 |
> problem? I've attached it to this letter. |
| 52 |
> |
| 53 |
> test # cat .config | grep XEN |
| 54 |
> CONFIG_XEN=y |
| 55 |
> CONFIG_XEN_DOM0=y |
| 56 |
> CONFIG_XEN_PRIVILEGED_GUEST=y |
| 57 |
> CONFIG_XEN_PVHVM=y |
| 58 |
> CONFIG_XEN_MAX_DOMAIN_MEMORY=128 |
| 59 |
> CONFIG_XEN_SAVE_RESTORE=y |
| 60 |
> # CONFIG_XEN_DEBUG_FS is not set |
| 61 |
> CONFIG_PCI_XEN=y |
| 62 |
> CONFIG_XEN_PCIDEV_FRONTEND=y |
| 63 |
> CONFIG_XEN_BLKDEV_FRONTEND=y |
| 64 |
> CONFIG_NETXEN_NIC=m |
| 65 |
> CONFIG_XEN_NETDEV_FRONTEND=y |
| 66 |
> CONFIG_HVC_XEN=y |
| 67 |
> CONFIG_XEN_BALLOON=y |
| 68 |
> CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y |
| 69 |
> CONFIG_XEN_SCRUB_PAGES=y |
| 70 |
> CONFIG_XEN_DEV_EVTCHN=y |
| 71 |
> # CONFIG_XEN_BACKEND is not set |
| 72 |
> CONFIG_XENFS=y |
| 73 |
> CONFIG_XEN_COMPAT_XENFS=y |
| 74 |
> CONFIG_XEN_SYS_HYPERVISOR=y |
| 75 |
> CONFIG_XEN_XENBUS_FRONTEND=y |
| 76 |
> CONFIG_XEN_GNTDEV=m |
| 77 |
> CONFIG_XEN_GRANT_DEV_ALLOC=m |
| 78 |
> CONFIG_SWIOTLB_XEN=y |
| 79 |
> |
| 80 |
> -- |
| 81 |
> Konstantin |
Archives