Re: [Xen-users] booting domU with current xen-unstable?

[Tom Brown <tbrown@xxxxxxxxxxxxx>]

On Fri, 30 Sep 2005, Jeffrey Buell wrote:

> I haven't been able to boot a domU using the current xen-unstable on x86 for
> over 2 weeks.  I'm building xen and the kernels from source using the default
> configs.  My last try was changeset 7145.  dom0 boots but when I try to boot
> domU I don't see any error messages but can't connect to the console.  xentop
> says that domU is up and using 100% CPU.  Is this just part of the
> development cycle or is anybody else able to use the current xen-unstable?

I tried a couple of days ago but couldn't get a domU to run, there was a
pause during the boot while trying to initialize the xen block device
driver, which timed out, and then of course it couldn't open it's root
device. There is already a buzilla call open about that.

   http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176

key points to me were:

   xen_blk: Initialising virtual block device driver
   xen_blk: Timeout connecting to device!
<snip>
   VFS: Cannot open root device "hda1" or unknown-block(2,0)
   Please append a correct "root=" boot option

that bug was closed 2005-08-25, but re-opened 10 days ago. Seems
to be tagged as 'critical'. 2.0-testing runs fine on my box,
which is just a pretty standard dual xeon supermicro machine...
6013pt :-)  (4 gig of memory though, that might be a tich
unusual.)

I _really_ _really_ want to be able to run SMP guests, so I've
been holding of on staging this box. If the developers want
access, that can be arranged.

-Tom



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users