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


Re: [Xen-users] Handling xvd device naming

To: Caleb Tennis <caleb.tennis@xxxxxxxxx>
Subject: Re: [Xen-users] Handling xvd device naming
From: "Fajar A. Nugraha" <list@xxxxxxxxx>
Date: Thu, 24 Feb 2011 20:03:48 +0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 24 Feb 2011 05:05:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7B4E0854-DFC0-4941-8AE4-1EE69C50F7BE@xxxxxxxxx>
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>
References: <7B4E0854-DFC0-4941-8AE4-1EE69C50F7BE@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Feb 24, 2011 at 7:49 PM, Caleb Tennis <caleb.tennis@xxxxxxxxx> wrote:
> We've been running fedora 13 within EC2 now for a while and have started 
> running into kernel OOPses with a certain combination of our tools, and it 
> looks to be a result of needing a more recently patched kernel to fix a Xen 
> bug or two.  Ok, no problem.
> I've upgraded our kernel to the latest xen (have also tried 
> from jeremy's sources.  This works great, however, all of my xvd* 
> devices have shifted.
> That is, what used to be /dev/xvda in the domU is now /dev/xvde in the domU. 
>  The vdb numbers are the same, but for some reason everything has shifted 64 
> minor numbers (202,1 -> 202,65, for example).
> I don't know if this is Xen, or something local to the machine, like udev, 
> but I'm asking here if anyone knows a nice or easy way to solve this?

Do you have access to Amazon's domU config file by any chance? Just
guessing, the config file might be using hda.

I had a similar problem using Oracle's kernel-uek on RHEL5 PV domU.
Turns out in my case the problem only happens when my domU config file
uses hda. When I change domU config file to use xvda it works just
fine. As a workaround, you can change fstab and grub.conf to use LABEL
or UUID so it wouldn't matter what device name they actually appear

BTW, (202,1) is xvda1, not xvda.


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>