On Tue, Mar 23, 2010 at 04:24:43PM -0700, Andrew Evans wrote:
> On 03/22/10 12:54, Pasi Kärkkäinen wrote:
> > Are you sure you got the earlier xen 3.4.x stuff completely removed?
> > Did you also make sure virt-manager, libvirt, virsh etc were downgraded
> > to the RHEL5 default versions?
> >
>
> You were right again. libvirt-0.7.2 built against Xen 3.3.1 was
> preventing the RHEL 5 Xen 3.1.2 xend from working.
>
Ok.
> > Dunno if the xml configuration created with newer libvirt is still
> > compatible
> > with the older libvirt/xen..
> >
>
> That was also a problem. I had to add a <uuid> tag as libvirt wouldn't
> generate one by default, and a <console> tag to get access to the serial
> console again.
>
> So...after all that, same problem: the domU fails to find the root
> filesystem, just as with the gitco xen-3.4.2 RPMs. If I omit
> 'hda=noprobe' from the kernel command line, the domU boots, using
> /dev/hd* via the ide-disk driver. I can then mount the virtual disks via
> /dev/xvd*, so at that point xen-vbd is working.
>
When it also happens with the vanilla EL5 stuff, it might be worth opening a bug
in redhat's bugzilla, and put all the details there.
-- Pasi
> I'm going to put this aside for now. I'll hopefully be trying a pv_ops
> dom0 kernel soon. Hopefully I can get a RHEL 5 domU to boot from
> /dev/xvd* with that setup.
>
> Thanks for all your help.
>
> -Andrew
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|