Hi, I have a test box running FC5 (kernel-xen0-2.6.18-1.2200.fc5) with a FC5 guest system. I upgraded the host to FC6, and am now running the FC6 Xen kernel (kernel-xen-2.6.18-1.2798.fc6). I am now unable to run the guest system. I see the following msgs in the log: ERROR: Non PAE-kernel on PAE host. ERROR: Error constructing guest OS I''ve googled and found this [1]: Q. When creating a guest the message "Invalid argument" is displayed. A. This usually indicates that the kernel image you are trying to boot is incompatible with the hypervisor. This will be seen if trying to run a FC5 (non-PAE) kernel on FC6 (which is PAE only), or if trying to run a bare metal kernel. [1] http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 I''m guessing the fix is to upgrade the guest O/S to FC6 too. However, I am currently unable to boot it as it won''t boot under FC6 and the FC6 version of Xen won''t run under the FC5 kernel. Any suggestions as to how I might fix this? Or did I basically do things in the wrong order, i.e. should I have upgraded the guest O/S first? Thanks, R. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robin, The kernel-xen package is PAE-enabled kernel in FC5 too I believe, so you need to upgrade the kernel in your domU to that. (however, the kernel-xen0 and kernel-xenU packages, as you''ve found, aren''t PAE) I see 2 alternatives here (in both cases, back up the domU image first using dd or similar): 1. Try the FC5 to FC6 upgrade process by running xenguest-install with FC6, against the FC5 disk image. I''m not sure if the upgrade process works or 2. More involved, but using rpm to install the PAE-enabled kernel-xen from FC5.. read on :) You can do that by mounting the domU''s filesystem - either using lomount if you''re using a file-based image, or kpartx if you''re using an LVM-based image. e.g. to mount the partitions in an Logical volume called "domU1" which resides in a physical volume "LogVol00", I''d use something like: kpartx -av /dev/LogVol00/domU1 It''ll then create mapper entries in /dev/mapper/ to each partition which you can in turn mount inside the dom0. (if the domU''s virtual disk is also LVM-based, you can use kpartx again on the entry in /dev/mapper that corresponds to the LV partition - although this can get messy if you''ve left volume names as the default in all dom''s). You''ll need to mount the root partition, and /boot and maybe also create a /proc filesystem (mount -t proc proc /mnt/domUroot/proc). Fetch yourself the rpm for kernel-xen from an updates repository, then use rpm with the --root flag to upgrade the kernel.. e.g. something like rpm -ivh --root /mnt/domUroot kernel-xen-2.6.18-1.2200.fc5.i686.rpm Once that completes, you should be able to unmount all the partitions, and use "kpartx -dv /dev/LogVol00/domU1" to remove the mapper entries. Once they''re gone, try booting the domU and it should work. Man pages for each of the commands above will help if you get stuck on syntax or semantics :) HTH Hilton. Robin Bowes wrote:> Hi, > > I have a test box running FC5 (kernel-xen0-2.6.18-1.2200.fc5) with a FC5 > guest system. > > I upgraded the host to FC6, and am now running the FC6 Xen kernel > (kernel-xen-2.6.18-1.2798.fc6). > > I am now unable to run the guest system. I see the following msgs in the > log: > > ERROR: Non PAE-kernel on PAE host. > ERROR: Error constructing guest OS > > I''ve googled and found this [1]: > > Q. When creating a guest the message "Invalid argument" is displayed. > > A. This usually indicates that the kernel image you are trying to boot > is incompatible with the hypervisor. This will be seen if trying to run > a FC5 (non-PAE) kernel on FC6 (which is PAE only), or if trying to run a > bare metal kernel. > > [1] http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 > > > I''m guessing the fix is to upgrade the guest O/S to FC6 too. However, I > am currently unable to boot it as it won''t boot under FC6 and the FC6 > version of Xen won''t run under the FC5 kernel. > > Any suggestions as to how I might fix this? Or did I basically do things > in the wrong order, i.e. should I have upgraded the guest O/S first? > > Thanks, > > R. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hilton Day wrote:> Robin, > > The kernel-xen package is PAE-enabled kernel in FC5 too I believe, so > you need to upgrade the kernel in your domU to that. (however, the > kernel-xen0 and kernel-xenU packages, as you''ve found, aren''t PAE) > > I see 2 alternatives here (in both cases, back up the domU image first > using dd or similar): > > 1. Try the FC5 to FC6 upgrade process by running xenguest-install with > FC6, against the FC5 disk image. I''m not sure if the upgrade process works > > or 2. More involved, but using rpm to install the PAE-enabled > kernel-xen from FC5.. read on :)Hilton, Thanks for the detailed instructions. I wasn''t going to bother fixing this as it''s only a test system - I thought I''d just make a mental note to use kernel-xen on my guests in future. But, the challenge got too much for me so I had a go! Here''s what I did: mkdir /mnt/guest1 losetup /dev/loop0 /home/xen/disks/guest1 kpartx -av /dev/loop0 vgchange -ay mount /dev/VolGroup00/LogVol00 /mnt/guest1 mount /dev/mapper/loop0p1 /mnt/guest1/boot/ mount -t proc proc /mnt/guest1/proc mount -t sysfs sys /mnt/guest1/sys wget http://example.com/path/to/kernel-xen-2.6.18-1.2200.fc5.i686.rpm rpm -ivh --root /mnt/guest1 kernel-xen-2.6.18-1.2200.fc5.i686.rpm perl -pi -e ''s/^default=1/default=0/'' /mnt/guest1/boot/grub/grub.conf umount /mnt/guest1/sys umount /mnt/guest1/dev umount /mnt/guest1/proc umount /mnt/guest1/boot umount /mnt/guest1 vgchange -an VolGroup00 kpartx -dv /dev/loop0 losetup -d /dev/loop0 I then tried to start the guest: # xm create /etc/xen/auto/guest1 Using config file "/etc/xen/auto/guest1". Going to boot Fedora Core (2.6.18-1.2200.fc5xen) kernel: /xen.gz-2.6.18-1.2200.fc5-PAE Error: (22, ''Invalid argument'') I see this msg in xend-debug.log: ERROR: Not a Xen-ELF image: No ELF notes or ''__xen_guest'' section found. ERROR: Error constructing guest OS So, the kernel''s installed but it won''t boot. Any further ideas? R. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bump. Any idea what''s wrong? Thanks, R. Robin Bowes wrote:> Hilton Day wrote: >> Robin, >> >> The kernel-xen package is PAE-enabled kernel in FC5 too I believe, so >> you need to upgrade the kernel in your domU to that. (however, the >> kernel-xen0 and kernel-xenU packages, as you''ve found, aren''t PAE) >> >> I see 2 alternatives here (in both cases, back up the domU image first >> using dd or similar): >> >> 1. Try the FC5 to FC6 upgrade process by running xenguest-install with >> FC6, against the FC5 disk image. I''m not sure if the upgrade process works >> >> or 2. More involved, but using rpm to install the PAE-enabled >> kernel-xen from FC5.. read on :) > > Hilton, > > Thanks for the detailed instructions. > > I wasn''t going to bother fixing this as it''s only a test system - I > thought I''d just make a mental note to use kernel-xen on my guests in > future. But, the challenge got too much for me so I had a go! > > Here''s what I did: > > mkdir /mnt/guest1 > losetup /dev/loop0 /home/xen/disks/guest1 > kpartx -av /dev/loop0 > vgchange -ay > mount /dev/VolGroup00/LogVol00 /mnt/guest1 > mount /dev/mapper/loop0p1 /mnt/guest1/boot/ > mount -t proc proc /mnt/guest1/proc > mount -t sysfs sys /mnt/guest1/sys > wget http://example.com/path/to/kernel-xen-2.6.18-1.2200.fc5.i686.rpm > rpm -ivh --root /mnt/guest1 kernel-xen-2.6.18-1.2200.fc5.i686.rpm > perl -pi -e ''s/^default=1/default=0/'' /mnt/guest1/boot/grub/grub.conf > umount /mnt/guest1/sys > umount /mnt/guest1/dev > umount /mnt/guest1/proc > umount /mnt/guest1/boot > umount /mnt/guest1 > vgchange -an VolGroup00 > kpartx -dv /dev/loop0 > losetup -d /dev/loop0 > > I then tried to start the guest: > > # xm create /etc/xen/auto/guest1 > Using config file "/etc/xen/auto/guest1". > Going to boot Fedora Core (2.6.18-1.2200.fc5xen) > kernel: /xen.gz-2.6.18-1.2200.fc5-PAE > Error: (22, ''Invalid argument'') > > I see this msg in xend-debug.log: > > ERROR: Not a Xen-ELF image: No ELF notes or ''__xen_guest'' section found. > ERROR: Error constructing guest OS > > So, the kernel''s installed but it won''t boot. > > Any further ideas? > > R._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users