Ok, i just tried this on RHEL 5 (3.0.3) to see what the issue is.
I installed the normal kernel on domU, like you did.
Adjusted the config to go off of the HVM and 64 bit device_model.
It still just hung. Then I realized the key difference between that
file and my other HVM's. Its the vif line. I had to specify the type
of "ioemu"
vif = [ 'mac=00:16:3e:3f:a9:f5, type=ioemu, bridge=xenbr1', ]
I ran into partition problems though and get a kernel panic immediately
after boot because the PV domU was using xvda not hda. I'm running into
more and more issues because the domU guest is fedora which uses labels
for disks. It looks like my initrd is not pointing to the correct
devices and I'll need to change my fstab and grub.conf.
Its still not working, but it at least gets you passed the step that
your on. I don't know if i'll have time today to work through the
partition issues or not, but if you are running a non redhat flavor on
your domU you might not even have these problems.
my config:
name = "test"
memory = "256"
vcpus=1
apic=1
acpi=1
pae=1
builder = "hvm"
device_model = "/usr/lib64/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
disk = [ 'file:/xen/linux/f7/test/test.img,hda,w', ]
vif = [ 'mac=00:16:3e:4f:04:01, type=ioemu, bridge=xenbr3', ]
#vfb = ["type=vnc,vncunused=1,vnclisten=0.0.0.0"]
vnc=1
vncunused=1
#vncdisplay=7
on_reboot = 'restart'
on_crash = 'restart'
On Tue, 2007-08-07 at 08:59 +0200, Riccardo Veraldi wrote:
> Yes it hangs anyway...
>
> I think on Fedora 7 Xen is version 3.1 while on my distribution
> I still have Xen 3.0.3
>
> thanks anyway.
>
> Riccardo
>
>
> Jason Solan wrote:
> > I can't say that I've tried moving a PV 32 bit to HVM 32 bit on RHEL 5
> > 64 bit, but i have done it on fedora 7. I feel pretty comfortable
> > saying that it should work the same on RHEL 5.
> >
> > With a 64 bit dom0 I've found that the device_model has to be the lib64
> > version or it hangs (similar to the issue you're seeing). Do you have
> > any fully virtualized domU's on this system?
> >
> > I suggest trying:
> >
> > device_model = "/usr/lib64/xen/bin/qemu-dm"
> >
> >
> >
> > On Mon, 2007-08-06 at 19:57 +0200, Riccardo Veraldi wrote:
> >
> >> Hello,
> >> I have a 64 bit dom0 with RHEL5
> >>
> >> I have a 32 bit domU para virtualized
> >>
> >> I want to bring it on my new dom0
> >>
> >> so I installed a non xen kernel on the domU
> >> and I copyed the image file on hte dom0
> >>
> >> I changed the /etc/xen/myhost accordingly
> >>
> >> but when I start the domain it hangs and nothing happens
> >>
> >> here is
> >>
> >> /etc/xen/sympa5_3_2
> >>
> >> name = "sympa5_3_2"
> >> builder = "hvm"
> >> memory = "1024"
> >> disk = [ 'file:/xen/domU/sympa5_3_2,hda,w', ]
> >> vif = [ 'mac=00:16:3e:3f:a9:f5, bridge=xenbr1', ]
> >> vfb = ["type=vnc,vncunused=1"]
> >> uuid = "ffc68565-354a-32da-7302-72a1bd5ff1af"
> >> device_model = "/usr/lib/xen/bin/qemu-dm"
> >> kernel = "/usr/lib/xen/boot/hvmloader"
> >> vcpus=1
> >> on_reboot = 'restart'
> >> on_crash = 'restart'
> >>
> >>
> >> I Also took a qemu-dm and used it insted of the default one which is 64bit
> >>
> >> [root@xenserver2 xen]# xm create /etc/xen/sympa5_3_2 -c
> >> Using config file "/etc/xen/sympa5_3_2".
> >>
> >>
> >> nothing happens:
> >> [root@xenserver2 ~]# xm list
> >> Name ID Mem(MiB) VCPUs State Time(s)
> >> Domain-0 0 2976 4 r----- 605.2
> >> sympa5_3_2 10 1030 1 --p--- 0.0
> >>
> >> [root@xenserver2 ~]# xm unpause sympa5_3_2
> >>
> >> [root@xenserver2 ~]# xm list
> >> Name ID Mem(MiB) VCPUs State Time(s)
> >> Domain-0 0 2976 4 r----- 605.5
> >> sympa5_3_2 10 1030 1 ------ 0.0
> >>
> >> bit nothing happens.
> >>
> >> is there a way so that I Can bring my domU running on a 32 bit dom0
> >> para virtualized on my new 64 bit xen fully virtualized dom0 ?
> >>
> >> thanks a lot
> >>
> >> Rick
> >>
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-users
> >>
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|