[Xen-users] block node 202 in maverick domU

[Mark Pryor <tlviewer@xxxxxxxxx>]

Hello,

this subject came up yesterday in ##xen@xxxxxxxxxxxx

In an Ubuntu 10.10 (maverick) domU, using /dev/xvda in

------------- mavU.cfg ---------
disk = [ "phy:/dev/VG/mavU,xvda,w" ]

# 
------ snip cfg ------

leads to 
`rootfs not found` errors and the domU will not finish booting.

However, changing xvda->sda works, as long as its done in config, fstab, and 
perhaps in menu.lst/grub.cfg, unless blkid's are used.

What's really happening here?
---------------
Looking at /proc/devices, specifically block 202, reserved for Xen, you can see 
that maverick has `sd`, not `xvda`.

My question is, is this a bug or a feature? 
It has come a handful of times in irc channel, but I've seen no discussion 
anywhere else.

Any ideas why suddenly Ubuntu did this? Lucid follows the tradition and uses 
xvda. Is this controlled in udev or kernel, or both?

-- 
Mark






      

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