Re: [Xen-users] Handling xvd device naming

[Caleb Tennis <caleb.tennis@xxxxxxxxx>]

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

> 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?

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