Hi,
Anyone got any tips on getting a fc5 domU to load on a rhel dom0? I've been struggling with it all morning. I'm stuck at:
--- config --- memory = "1024" disk = [ 'phy:/dev/x/aaa,xvda,w' ] vif = [ 'mac=00:aa:bb:cc:dd:ee' ] uuid = "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee" bootloader="/usr/bin/pygrub" --- end ---
--- domU grub --- title Fedora Core (2.6.20-1.2307.fc5xen) root (hd0,0) kernel /vmlinuz-2.6.20-1.2307.fc5xen ro root=/dev/gui/r rhgb quiet initrd /initrd-2.6.20-1.2307.fc5xen-blk.img --- end ---
(Original domU was using fc5xenU kernel/initrd, but google told me I needed this PAE kernel. It fixed the PAE errors I was getting in xend-debug initially.)
--- stdout --- Going to boot Fedora Core (2.6.20-1.2307.fc5xen) kernel: /vmlinuz-2.6.20-1.2307.fc5xen initrd: /initrd-2.6.20-1.2307.fc5xen-rs.img Started domain gui PCI: Fatal: No config space access function found rtc: IRQ 8 is not free. PCI: Fatal: No config space access function found rtc: IRQ 8 is not free. i8042.c: No controller found. Red Hat nash version 5.0.32 starting mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! --- end ---
--- xend-debug.log --- DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' --- end ---
Based on some googling, I made a custom initrd image with '--with xenblk --preload xenblk', but it didn't help any.. Any hints greatly appreciated...
Robert Story rstory-l@2006.revelstone.com writes:
Hi,
Anyone got any tips on getting a fc5 domU to load on a rhel dom0? I've been
Doesn't virt-install just work?
struggling with it all morning. I'm stuck at:
--- config --- memory = "1024" disk = [ 'phy:/dev/x/aaa,xvda,w' ] vif = [ 'mac=00:aa:bb:cc:dd:ee' ] uuid = "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee" bootloader="/usr/bin/pygrub" --- end ---
--- domU grub --- title Fedora Core (2.6.20-1.2307.fc5xen) root (hd0,0) kernel /vmlinuz-2.6.20-1.2307.fc5xen ro root=/dev/gui/r rhgb quiet initrd /initrd-2.6.20-1.2307.fc5xen-blk.img --- end ---
(Original domU was using fc5xenU kernel/initrd, but google told me I needed this PAE kernel. It fixed the PAE errors I was getting in xend-debug initially.)
--- stdout --- Going to boot Fedora Core (2.6.20-1.2307.fc5xen) kernel: /vmlinuz-2.6.20-1.2307.fc5xen initrd: /initrd-2.6.20-1.2307.fc5xen-rs.img Started domain gui PCI: Fatal: No config space access function found rtc: IRQ 8 is not free. PCI: Fatal: No config space access function found rtc: IRQ 8 is not free. i8042.c: No controller found. Red Hat nash version 5.0.32 starting mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! --- end ---
--- xend-debug.log --- DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' --- end ---
Based on some googling, I made a custom initrd image with '--with xenblk --preload xenblk', but it didn't help any.. Any hints greatly appreciated...
How did you install the PAE kernel? With rpm in the domU?
On Fri, 20 Apr 2007 17:28:42 +0200 Markus wrote: MA> Robert Story rstory-l@2006.revelstone.com writes: MA> > Anyone got any tips on getting a fc5 domU to load on a rhel dom0? I've been MA> MA> Doesn't virt-install just work?
I'm trying to get an existing domU from fc5 to load on rhel, not create a new one.
MA> > Based on some googling, I made a custom initrd image with '--with xenblk MA> > --preload xenblk', but it didn't help any.. Any hints greatly appreciated... MA> MA> How did you install the PAE kernel? With rpm in the domU?
I mounted the domU fs in the dom0, copied in the rpm, did a chroot, and rpm -i.
I finally got it working... turns out that the chroot was the problem.. once I did the mkinitrd w/out the chroot (pointed at the domU fstab), things started going a lot more smoothly...
So, the good news is that I got it working... the bad news seems to be that everytime I want to update the domU kernel, I have to install it, shut down the domU, loop mount domU, create custom initrd and reboot. Rinse and repeat for each fc5 domU. If anyone has a way that this can be done within the domU so I can automate it w/out having to go to the dom0, that would be great..
Robert Story rstory-l@2006.revelstone.com writes:
On Fri, 20 Apr 2007 17:28:42 +0200 Markus wrote: MA> Robert Story rstory-l@2006.revelstone.com writes: MA> > Anyone got any tips on getting a fc5 domU to load on a rhel dom0? I've been MA> MA> Doesn't virt-install just work?
I'm trying to get an existing domU from fc5 to load on rhel, not create a new one.
MA> > Based on some googling, I made a custom initrd image with '--with xenblk MA> > --preload xenblk', but it didn't help any.. Any hints greatly appreciated... MA> MA> How did you install the PAE kernel? With rpm in the domU?
I mounted the domU fs in the dom0, copied in the rpm, did a chroot, and rpm -i.
I finally got it working... turns out that the chroot was the problem.. once I did the mkinitrd w/out the chroot (pointed at the domU fstab), things started going a lot more smoothly...
So, the good news is that I got it working... the bad news seems to be that everytime I want to update the domU kernel, I have to install it, shut down the domU, loop mount domU, create custom initrd and reboot. Rinse and repeat for each fc5 domU. If anyone has a way that this can be done within the domU so I can automate it w/out having to go to the dom0, that would be great..
I update my domUs by running rpm (actually yum) in the domU. Works fine for me.
On Sat, 21 Apr 2007, Markus Armbruster wrote:
So, the good news is that I got it working... the bad news seems to be that everytime I want to update the domU kernel, I have to install it, shut down the domU, loop mount domU, create custom initrd and reboot. Rinse and repeat for each fc5 domU. If anyone has a way that this can be done within the domU so I can automate it w/out having to go to the dom0, that would be great..
I update my domUs by running rpm (actually yum) in the domU. Works fine for me.
That only works for "xen aware" OS'es. It won't work to run FC/RHEL 3/4.
Paul
On Sat, 21 Apr 2007 01:29:51 +0200 (CEST) Paul wrote: PW> On Sat, 21 Apr 2007, Markus Armbruster wrote: PW> PW> > > So, the good news is that I got it working... the bad news seems to be that PW> > > everytime I want to update the domU kernel, I have to install it, shut down PW> > > the domU, loop mount domU, create custom initrd and reboot. Rinse and PW> > > repeat for each fc5 domU. If anyone has a way that this can be done within the PW> > > domU so I can automate it w/out having to go to the dom0, that would be great.. PW> > PW> > I update my domUs by running rpm (actually yum) in the domU. Works PW> > fine for me. PW> PW> That only works for "xen aware" OS'es. It won't work to run FC/RHEL 3/4.
It doesn't seem to be working for me with fc5 either... It just so happened that there was a fc5 kernel release (2312) yesterday or today, after I got 2307 up and running. I did the yum update in the domU, but after a domU shutdown and xm create, the domU wouldn't come back up again. I don't remember the details, but the procedure above got me back in business. I'll try to remember to take note of what fails when the next update happens (If I haven't moved that domain to fc6 by then).
Robert Story rstory-l@2006.revelstone.com writes:
On Sat, 21 Apr 2007 01:29:51 +0200 (CEST) Paul wrote: PW> On Sat, 21 Apr 2007, Markus Armbruster wrote: PW> PW> > > So, the good news is that I got it working... the bad news seems to be that PW> > > everytime I want to update the domU kernel, I have to install it, shut down PW> > > the domU, loop mount domU, create custom initrd and reboot. Rinse and PW> > > repeat for each fc5 domU. If anyone has a way that this can be done within the PW> > > domU so I can automate it w/out having to go to the dom0, that would be great.. PW> > PW> > I update my domUs by running rpm (actually yum) in the domU. Works PW> > fine for me. PW> PW> That only works for "xen aware" OS'es. It won't work to run FC/RHEL 3/4.
It doesn't seem to be working for me with fc5 either... It just so happened that there was a fc5 kernel release (2312) yesterday or today, after I got 2307 up and running. I did the yum update in the domU, but after a domU shutdown and xm create, the domU wouldn't come back up again. I don't remember the details, but the procedure above got me back in business. I'll try to remember to take note of what fails when the next update happens (If I haven't moved that domain to fc6 by then).
What exactly did you do? Which kernel (exact name and version) failed to install correctly in your domU? Is it reproducible by forcing a reinstall?
On Sat, 21 Apr 2007, Markus Armbruster wrote:
PW> That only works for "xen aware" OS'es. It won't work to run FC/RHEL 3/4.
It doesn't seem to be working for me with fc5 either... It just so happened that there was a fc5 kernel release (2312) yesterday or today, after I got 2307 up and running. I did the yum update in the domU, but after a domU shutdown and xm create, the domU wouldn't come back up again. I don't remember the details, but the procedure above got me back in business. I'll try to remember to take note of what fails when the next update happens (If I haven't moved that domain to fc6 by then).
What exactly did you do? Which kernel (exact name and version) failed to install correctly in your domU? Is it reproducible by forcing a reinstall?
I use the latest fedora-xen kernel of the dom0 to run the xenu's. Even to get those to run with FC3 is relatively easy, and mostly involves getting newer module-init-tools and udev/hotplug disabled (you don't need since you have no real hardware, but older nash-hotplug gets confused)
Paul
It doesn't seem to be working for me with fc5 either... It just so happened that there was a fc5 kernel release (2312) yesterday or today, after I got 2307 up and running. I did the yum update in the domU, but after a domU shutdown and xm create, the domU wouldn't come back up again. I don't remember the details, but the procedure above got me back in business. I'll try to remember to take note of what fails when the next update happens (If I haven't moved that domain to fc6 by then).
It's likely that you are missing something from your /etc/modprobe.conf; when the kernel is installed via yum, one of the last things it does is dynamically generate an initrd based on your current configuration in /etc/modprobe.conf
The modprobe.conf on my (working) FC5 guest looks like this:
alias eth0 xennet alias scsi_hostadapter xenblk
What does yours look like?
Chris Lalancette
On Sat, 21 Apr 2007 09:22:16 -0400 Chris wrote: CL> > It doesn't seem to be working for me with fc5 either... CL> CL> It's likely that you are missing something from your /etc/modprobe.conf; CL> when the kernel is installed via yum, one of the last things it does is CL> dynamically generate an initrd based on your current configuration in CL> /etc/modprobe.conf CL> CL> The modprobe.conf on my (working) FC5 guest looks like this: CL> CL> alias eth0 xennet CL> alias scsi_hostadapter xenblk
Hmmm... I had the eth0 line in both my domUs, but the scsi line was only in one. IIRC, it was missing from the one I first tried the recent update on, so that may have been it. We'll find out when the next kernel update comes out!
Paul Wouters paul@xelerance.com writes:
On Sat, 21 Apr 2007, Markus Armbruster wrote:
So, the good news is that I got it working... the bad news seems to be that everytime I want to update the domU kernel, I have to install it, shut down the domU, loop mount domU, create custom initrd and reboot. Rinse and repeat for each fc5 domU. If anyone has a way that this can be done within the domU so I can automate it w/out having to go to the dom0, that would be great..
I update my domUs by running rpm (actually yum) in the domU. Works fine for me.
That only works for "xen aware" OS'es. It won't work to run FC/RHEL 3/4.
I'm confused. We're talking about para-virtual guests, aren't we? How can you use an OS that is not `xen aware' in a para-virtual guest?
On Fri, 20 Apr 2007, Robert Story wrote:
I'm trying to get an existing domU from fc5 to load on rhel, not create a new one.
MA> > Based on some googling, I made a custom initrd image with '--with xenblk MA> > --preload xenblk', but it didn't help any.. Any hints greatly appreciated... MA> MA> How did you install the PAE kernel? With rpm in the domU?
So, the good news is that I got it working... the bad news seems to be that everytime I want to update the domU kernel, I have to install it, shut down the domU, loop mount domU, create custom initrd and reboot. Rinse and repeat for each fc5 domU. If anyone has a way that this can be done within the domU so I can automate it w/out having to go to the dom0, that would be great..
RedHat is unwilling to fix this:
https://www.redhat.com/archives/fedora-xen/2007-April/msg00054.html
Perhaps some people should get together and start a yum repository to address this issue through alternative means.
Paul
-
Chris Lalancette -
Markus Armbruster -
Paul Wouters -
Robert Story