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 2.6.32.27 (have also tried 2.6.32.25) 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? Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Feb 24, 2011 at 7:49 PM, Caleb Tennis <caleb.tennis@gmail.com> 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 2.6.32.27 (have also tried 2.6.32.25) 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 as. BTW, (202,1) is xvda1, not xvda. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > 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@lists.xensource.com http://lists.xensource.com/xen-users