RE: [Xen-devel] Resolved - domU won't recognise my block devices - James Harper - com.xensource.lists.xen-devel

5 messages in com.xensource.lists.xen-develRE: [Xen-devel] Resolved - domU won't...

From	Sent On	Attachments
James Harper	01 Dec 2005 21:41
M.A. Williamson	02 Dec 2005 09:33
James Harper	02 Dec 2005 15:14
Ian Pratt	02 Dec 2005 15:23
James Harper	02 Dec 2005 16:26

Subject:	RE: [Xen-devel] Resolved - domU won't recognise my block devices
From:	James Harper (jame...@bendigoit.com.au)
Date:	12/02/2005 03:14:34 PM
List:	com.xensource.lists.xen-devel

I tried using the xvd* devices in domU and it still didn't function. It got the major number right (202?) but claimed that it didn't see the device.

James

-----Original Message----- From: M.A. Williamson [mailto:maw...@hermes.cam.ac.uk] On Behalf Of M.A. Williamson Sent: Saturday, 3 December 2005 04:34 To: James Harper Cc: James Bulpin; Langsdorf, Mark; Ian Pratt; Xen- dev...@lists.xensource.com Subject: RE: [Xen-devel] Resolved - domU won't recognise my block devices

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

-----Original Message----- From: James Bulpin [mailto:jam...@xensource.com] Sent: Friday, 2 December 2005 04:19 To: Langsdorf, Mark Cc: Ian Pratt; James Harper; Xen-...@lists.xensource.com 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.

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.