RE: [Xen-devel] Resolved - domU won't recognise my block devices

["M.A. Williamson" <maw48@xxxxxxxxx>]

> Can someone please confirm that we should be building the -xen (not xen0
> + xenU) kernels and using those? If that's the case, then the default
> config is broken for me as devfs just doesn't work.
Arg, that's a bit broken... things shouldn't really be quite like that.

DevFS works fine in dom0 but breaks things within domUs... I don't know 
quite if it b0rks on the new xvd* devices, but certainly for hd* and sd* it 
will not work. Hmmm.
Given DevFS is deprecated, do we really need it in the default config?

Cheers,
Mark

> Of course, the initrd tools under debian want devfs, so to have a
> devfs-less kernel I had to move over to initramfs-tools... but my
> network booting off AoE is working nicely under that now after some
> tweaking...


> Thanks
>
> James
>
> > -----Original Message-----
> > From: James Bulpin [mailto:james@xxxxxxxxxxxxx]
> > Sent: Friday, 2 December 2005 04:19
> > To: Langsdorf, Mark
> > Cc: Ian Pratt; James Harper; Xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] domU won't recognise my block devices
> >
> > We're testing both 32 and 64 bit builds on a mixture of Xeon and
> > Opteron. Many of my colleagues use Opteron machines as their personal
> > test boxes as well. I've just fired off a test run explicitly on an
> > Opteron-based Sun V20z to make sure all is well: it it has booted and
> > started a guest just fine.
> >
> > Regards,
> > James
> >
> > Langsdorf, Mark wrote:
> > >>>No initrd. AoE is only used by dom0. Boot messages follow:
> > >>
> > >>It works for me... Are you sure you haven't borked your config?
> > >
> > >
> > > Ian, are you testing on Opterons in 64-bit mode or some other
> > > hardware?  One of the common themes in these bug reports (see
> > > also bugzilla #392) is 64-bit Opterons.  64-bit Intel Xeon
> > > does not seem to be affected in the same way.
> > >
> > > -Mark Langsdorf
> > > AMD, Inc.
> > >
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel