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

Re: [Xen-users] Handling xvd device naming

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Caleb Tennis <caleb.tennis@xxxxxxxxx>
  • Date: Thu, 24 Feb 2011 08:35:31 -0500
  • Delivery-date: Thu, 24 Feb 2011 05:40:34 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=uzPXMbU7N4lF8MLdl8nd60lNt0R4eFrxb7em1G7RUOHY+aDDBReeaxeuj+I0ZR+FWa z7h1JpEFrfNiy46wZIrRqtJiwzktMPyFXlbm+UpaeSAjnMGymo6WNZ2f3yG0Cr0rZfPX ommffkAc9dSljm9b3wBTHguujPdbERSsIpoDU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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

I don't have access to it.  However, other kernel versions work fine. (Fedora 
2.6.34 kernel doesn't have this behavior)

> 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
> as.

Yes, I can do this to boot up a test system, but our systems are currently 
structured under the original assumption and it would be a major feat to change 

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

Right, sorry, was just using as an example.  /dev/xvda1 -> /dev/xvde1 is what's 
happening in my case (and /dev/xvdb -> /dev/xvdf, etc)

So it sounds like maybe this is a new a feature of Xen at some point to map hda 
to xvde and later?

Xen-users mailing list



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