Re: DomU freezes in the middle of booting
Pandu Poluan <[email protected]> Thu, 12 Apr 2012 17:09:15 +0700
| Newsgroups | gmane.linux.gentoo.server |
|---|---|
| Message-ID | <CAA2qdGU__8xNV+RP+b1+hvyO9Kf32pvcH-9z5R9abMswa7idjQ@mail.gmail.com> |
--00221572766e63f4ea04bd788cd3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Apr 12, 2012 4:57 PM, "Konstantin" <[email protected]> wrote: > > Hello, > > With the help of Nikita, I've figured out how to get rid of > "xvda: unknown partition table" > > I have to use /dev/xvda1 not the /dev/xvda > > ------------------------------------- > disk =3D ['phy:/dev/vg01/vm0,xvda,w'] > root =3D '/dev/xvda ro' > ------------------------------------- > > changed to: > > ------------------------------------- > disk =3D ['phy:/dev/vg01/vm0,xvda1,w'] > root =3D '/dev/xvda1 ro' > ------------------------------------- > > Anyway booting freezes. Once I've saw: > > ------------------------------------- > TCP cubic registered > 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...190= s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...1= 35s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80= s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s..= .15s...10s...5s...0s... > XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 1) > XENBUS: Timeout connecting to device: device/vif/0 (local state 1, remote state 1) > VFS: Cannot open root device "xvda1" or unknown-block(0,0) > Please append a correct "root=3D" boot option; here are the available partitions: > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > Pid: 1, comm: swapper/0 Not tainted 3.2.12-gentoo #2 > Call Trace: > [<ffffffff81318ebd>] ? panic+0x92/0x199 > [<ffffffff81319004>] ? printk+0x40/0x4c > [<ffffffff814f4e2e>] ? mount_block_root+0x238/0x24f > [<ffffffff814f4fc0>] ? prepare_namespace+0x12c/0x156 > [<ffffffff814f4b3e>] ? kernel_init+0x10a/0x113 > [<ffffffff8131d074>] ? kernel_thread_helper+0x4/0x10 > [<ffffffff8131bd33>] ? int_ret_from_sys_call+0x7/0x1b > [<ffffffff8131b43c>] ? retint_restore_args+0x5/0x6 > [<ffffffff8131d070>] ? gs_change+0x13/0x13 > ------------------------------------- > > So I guess may be it's related to some DomU kernel configuration > problem? I've attached it to this letter. > > test # cat .config | grep XEN > CONFIG_XEN=3Dy > CONFIG_XEN_DOM0=3Dy > CONFIG_XEN_PRIVILEGED_GUEST=3Dy > CONFIG_XEN_PVHVM=3Dy > CONFIG_XEN_MAX_DOMAIN_MEMORY=3D128 > CONFIG_XEN_SAVE_RESTORE=3Dy > # CONFIG_XEN_DEBUG_FS is not set > CONFIG_PCI_XEN=3Dy > CONFIG_XEN_PCIDEV_FRONTEND=3Dy > CONFIG_XEN_BLKDEV_FRONTEND=3Dy > CONFIG_NETXEN_NIC=3Dm > CONFIG_XEN_NETDEV_FRONTEND=3Dy > CONFIG_HVC_XEN=3Dy > CONFIG_XEN_BALLOON=3Dy > CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=3Dy > CONFIG_XEN_SCRUB_PAGES=3Dy > CONFIG_XEN_DEV_EVTCHN=3Dy > # CONFIG_XEN_BACKEND is not set > CONFIG_XENFS=3Dy > CONFIG_XEN_COMPAT_XENFS=3Dy > CONFIG_XEN_SYS_HYPERVISOR=3Dy > CONFIG_XEN_XENBUS_FRONTEND=3Dy > CONFIG_XEN_GNTDEV=3Dm > CONFIG_XEN_GRANT_DEV_ALLOC=3Dm > CONFIG_SWIOTLB_XEN=3Dy > > -- > Konstantin Have you tried: root =3D '/dev/xvda1' That is, without 'ro'? Rgds, --00221572766e63f4ea04bd788cd3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p><br> On Apr 12, 2012 4:57 PM, "Konstantin" <<a href=3D"mailto:konst= [email protected]">[email protected]</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 =C2=A0 =3D ['phy:/dev/vg01/vm0,xvda,w']<br> > root =C2=A0 =3D '/dev/xvda ro'<br> > -------------------------------------<br> ><br> > changed to:<br> ><br> > -------------------------------------<br> > disk =C2=A0 =3D ['phy:/dev/vg01/vm0,xvda1,w']<br> > root =C2=A0 =3D '/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...17= 0s...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, rem= ote state 1)<br> > VFS: Cannot open root device "xvda1" or unknown-block(0,0)<b= r> > Please append a correct "root=3D" boot option; here are the = available partitions:<br> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl= ock(0,0)<br> > Pid: 1, comm: swapper/0 Not tainted 3.2.12-gentoo #2<br> > Call Trace:<br> > =C2=A0[<ffffffff81318ebd>] ? panic+0x92/0x199<br> > =C2=A0[<ffffffff81319004>] ? printk+0x40/0x4c<br> > =C2=A0[<ffffffff814f4e2e>] ? mount_block_root+0x238/0x24f<br> > =C2=A0[<ffffffff814f4fc0>] ? prepare_namespace+0x12c/0x156<br> > =C2=A0[<ffffffff814f4b3e>] ? kernel_init+0x10a/0x113<br> > =C2=A0[<ffffffff8131d074>] ? kernel_thread_helper+0x4/0x10<br> > =C2=A0[<ffffffff8131bd33>] ? int_ret_from_sys_call+0x7/0x1b<br> > =C2=A0[<ffffffff8131b43c>] ? retint_restore_args+0x5/0x6<br> > =C2=A0[<ffffffff8131d070>] ? gs_change+0x13/0x13<br> > -------------------------------------<br> ><br> > So I guess may be it's related to some DomU kernel configuration<b= r> > problem? I've attached it to this letter.<br> ><br> > test # cat .config | grep XEN<br> > CONFIG_XEN=3Dy<br> > CONFIG_XEN_DOM0=3Dy<br> > CONFIG_XEN_PRIVILEGED_GUEST=3Dy<br> > CONFIG_XEN_PVHVM=3Dy<br> > CONFIG_XEN_MAX_DOMAIN_MEMORY=3D128<br> > CONFIG_XEN_SAVE_RESTORE=3Dy<br> > # CONFIG_XEN_DEBUG_FS is not set<br> > CONFIG_PCI_XEN=3Dy<br> > CONFIG_XEN_PCIDEV_FRONTEND=3Dy<br> > CONFIG_XEN_BLKDEV_FRONTEND=3Dy<br> > CONFIG_NETXEN_NIC=3Dm<br> > CONFIG_XEN_NETDEV_FRONTEND=3Dy<br> > CONFIG_HVC_XEN=3Dy<br> > CONFIG_XEN_BALLOON=3Dy<br> > CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=3Dy<br> > CONFIG_XEN_SCRUB_PAGES=3Dy<br> > CONFIG_XEN_DEV_EVTCHN=3Dy<br> > # CONFIG_XEN_BACKEND is not set<br> > CONFIG_XENFS=3Dy<br> > CONFIG_XEN_COMPAT_XENFS=3Dy<br> > CONFIG_XEN_SYS_HYPERVISOR=3Dy<br> > CONFIG_XEN_XENBUS_FRONTEND=3Dy<br> > CONFIG_XEN_GNTDEV=3Dm<br> > CONFIG_XEN_GRANT_DEV_ALLOC=3Dm<br> > CONFIG_SWIOTLB_XEN=3Dy<br> ><br> > --<br> > Konstantin</p> <p>Have you tried:</p> <p> root =C2=A0 =3D '/dev/xvda1'</p> <p>That is, without 'ro'? </p> <p>Rgds, <br> </p> --00221572766e63f4ea04bd788cd3--