This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] block node 202 in maverick domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] block node 202 in maverick domU
From: Mark Pryor <tlviewer@xxxxxxxxx>
Date: Fri, 7 Jan 2011 17:56:54 -0800 (PST)
Delivery-date: Fri, 07 Jan 2011 17:58:13 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1294451814; bh=kf/NfVdlCnooFMDFVcCn7iEkUS5FY3whW7bv43QSWkI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=pzFdWcKwjsjyH6nBRKkFQ2/4vvkGjAjTUhU1ZrN2puF2xsHm/67bA4SOs+gifnVB6Jam/973yr1JG5KfxlBl6K+AfhCa7R73pXrSiebWh9zdasp23alZnNGrJIItZYtkZZRxYsbtCPvTwDmz1jySdRYhRLO4YkiEw2V10WfkOM8=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=hsmX1rMkLbGQme/vtsEEc6Wcq7CY4aSt4tSSkgJlFTEdzG0na+/XIz37YFuusbHwK5ynqEM5NGDnc+CxEjvmZZx87RaEFrgQTIe6MR+/o1b6kg36ECL/usS7/zOI1DSnwvKjDLJ8jw0jqbZBPAH5daYLOGa9tOgw4vL5Rmh6JnI=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

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?



Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] block node 202 in maverick domU, Mark Pryor <=