[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Handling xvd device naming

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Caleb Tennis <caleb.tennis@xxxxxxxxx>
  • Date: Thu, 24 Feb 2011 07:49:32 -0500
  • Delivery-date: Thu, 24 Feb 2011 04:51:04 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=xyx+ztZ9/igouvedJuEXfPfQNkvYJXV21LX4oecOLqhiKSEGYNrmrkQU1f1wZ/lBUs M4kPZFzSIvHpplc133tIC0Bucw+X3OzZvmlIXlSEdMnT903dazz42a8RNyFaHWBGSYTd c6U2/cdOCkrGPNik28eXmZ1JalJHFHTQ0UCCc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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?

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.