All,
I've had a heck of a time getting Fedora 16 to run as a guest VM under CentOS 5.7 host as a paravirtualized Xen guest. I believe the issue has something to do with Fedora 16 using grub2...
When I attempt to start the VM (via xm create), I get this error:
Using config file "/etc/xen/fedora-workstation". Traceback (most recent call last): File "/usr/bin/pygrub", line 686, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger "xend" Error: Boot loader didn't return any data!
In my kickstart, I had to create a partition for F16 as:
part biosboot --fstype=biosboot --size=1
I didn't readily find the error when googling...
Has anyone been able to run F16 as a PV guest? And if so, what did you do to make it happen?????
Thanks!!!!!!!!!!!!!
Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare
Sorry for the top post but I think it's appropriate here. The message below was posted 20th of December last year with no response. I've now hit the same problem.
I have CentOS 5.7 and and trying to install an F16 domU PV guest. It seems that pygrub is failing to read the grub2 setup.
It also seems that there is a fix for this in xen-3.0.3-135.el according to:
https://bugzilla.redhat.com/show_bug.cgi?id=746602
(pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1)
However, centos only has xen-3.0.3-132.el5_7.2 and so does not have the pygrub fixes and I'm not even sure RH has relased xen-3.0.3-135.el yet.
Has anyone found a way to install F16 as a domU guest on Centos 5.7?
On 20 December 2011 00:33, Scot P. Floess sfloess@nc.rr.com wrote:
All,
I've had a heck of a time getting Fedora 16 to run as a guest VM under CentOS 5.7 host as a paravirtualized Xen guest. I believe the issue has something to do with Fedora 16 using grub2...
When I attempt to start the VM (via xm create), I get this error:
Using config file "/etc/xen/fedora-workstation". Traceback (most recent call last): File "/usr/bin/pygrub", line 686, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger "xend" Error: Boot loader didn't return any data!
In my kickstart, I had to create a partition for F16 as:
part biosboot --fstype=biosboot --size=1
I didn't readily find the error when googling...
Has anyone been able to run F16 as a PV guest? And if so, what did you do to make it happen?????
Thanks!!!!!!!!!!!!!
Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
On Tue, 10 Jan 2012, Norman Gaywood wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=746602
(pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1)
why would one use GPT for a domU? seems like gross overkill
-- Russ herrold
On Mon, 2012-01-09 at 18:56 -0500, R P Herrold wrote:
On Tue, 10 Jan 2012, Norman Gaywood wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=746602
(pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1)
why would one use GPT for a domU? seems like gross overkill
-- Russ herrold
There are a bunch of grub2-related issues associated with F16 anaconda and one of the easiest ways to deal with them is to use gpt. There is a nogpt kernel option that may help, but I have not tried it.
Also, if left to itself, F16 anaconda will (apparently) use gpt.
http://fedoraproject.org/wiki/Common_F16_bugs
"Fedora 16 uses the newer GPT disk label format, when formatting an entire disk during installation."
I am running a gpt F16 guest under rhel6/kvm without issues.
Steve
On Mon, Jan 09, 2012 at 07:20:05PM -0500, S.Tindall wrote:
On Mon, 2012-01-09 at 18:56 -0500, R P Herrold wrote:
On Tue, 10 Jan 2012, Norman Gaywood wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=746602 (pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1)
why would one use GPT for a domU? seems like gross overkill
There are a bunch of grub2-related issues associated with F16 anaconda and one of the easiest ways to deal with them is to use gpt. There is a nogpt kernel option that may help, but I have not tried it.
Yes, GPT is the default for F16 so it is easier just to go with it. I have tried the nogpt option and F16 installs OK (as it does without it). However it still can't boot:
[root@dom0 ~]# sfdisk -d /dev/VM/f16 # partition table of /dev/VM/f16 unit: sectors
/dev/VM/f161 : start= 2048, size= 1024000, Id=83, bootable /dev/VM/f162 : start= 1026048, size= 40916992, Id=8e /dev/VM/f163 : start= 0, size= 0, Id= 0 /dev/VM/f164 : start= 0, size= 0, Id= 0 [root@dom0 ~]# pygrub -i /dev/VM/f16 Traceback (most recent call last): File "/usr/bin/pygrub", line 691, in ? chosencfg = run_grub(file, entry, fs) File "/usr/bin/pygrub", line 545, in run_grub g = Grub(file, fs) File "/usr/bin/pygrub", line 203, in __init__ self.read_config(file, fs) File "/usr/bin/pygrub", line 402, in read_config if self.cf.filename is None: AttributeError: Grub instance has no attribute 'cf'
The error is in the parsing of the grub2 config I believe.
Ditto on my end - I tried both with the same results you mention...
On Tue, 10 Jan 2012, Norman Gaywood wrote:
On Mon, Jan 09, 2012 at 07:20:05PM -0500, S.Tindall wrote:
On Mon, 2012-01-09 at 18:56 -0500, R P Herrold wrote:
On Tue, 10 Jan 2012, Norman Gaywood wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=746602 (pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1)
why would one use GPT for a domU? seems like gross overkill
There are a bunch of grub2-related issues associated with F16 anaconda and one of the easiest ways to deal with them is to use gpt. There is a nogpt kernel option that may help, but I have not tried it.
Yes, GPT is the default for F16 so it is easier just to go with it. I have tried the nogpt option and F16 installs OK (as it does without it). However it still can't boot:
[root@dom0 ~]# sfdisk -d /dev/VM/f16 # partition table of /dev/VM/f16 unit: sectors
/dev/VM/f161 : start= 2048, size= 1024000, Id=83, bootable /dev/VM/f162 : start= 1026048, size= 40916992, Id=8e /dev/VM/f163 : start= 0, size= 0, Id= 0 /dev/VM/f164 : start= 0, size= 0, Id= 0 [root@dom0 ~]# pygrub -i /dev/VM/f16 Traceback (most recent call last): File "/usr/bin/pygrub", line 691, in ? chosencfg = run_grub(file, entry, fs) File "/usr/bin/pygrub", line 545, in run_grub g = Grub(file, fs) File "/usr/bin/pygrub", line 203, in __init__ self.read_config(file, fs) File "/usr/bin/pygrub", line 402, in read_config if self.cf.filename is None: AttributeError: Grub instance has no attribute 'cf'
The error is in the parsing of the grub2 config I believe.
-- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia
ngaywood@une.edu.au Phone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~norm Fax: +61 (0)2 6773 3312
Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare
10.01.2012 4:33, Norman Gaywood пишет:
On Mon, Jan 09, 2012 at 07:20:05PM -0500, S.Tindall wrote:
On Mon, 2012-01-09 at 18:56 -0500, R P Herrold wrote:
On Tue, 10 Jan 2012, Norman Gaywood wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=746602 (pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1)
why would one use GPT for a domU? seems like gross overkill
There are a bunch of grub2-related issues associated with F16 anaconda and one of the easiest ways to deal with them is to use gpt. There is a nogpt kernel option that may help, but I have not tried it.
Yes, GPT is the default for F16 so it is easier just to go with it. I have tried the nogpt option and F16 installs OK (as it does without it). However it still can't boot:
[root@dom0 ~]# sfdisk -d /dev/VM/f16 # partition table of /dev/VM/f16 unit: sectors
/dev/VM/f161 : start= 2048, size= 1024000, Id=83, bootable /dev/VM/f162 : start= 1026048, size= 40916992, Id=8e /dev/VM/f163 : start= 0, size= 0, Id= 0 /dev/VM/f164 : start= 0, size= 0, Id= 0 [root@dom0 ~]# pygrub -i /dev/VM/f16 Traceback (most recent call last): File "/usr/bin/pygrub", line 691, in ? chosencfg = run_grub(file, entry, fs) File "/usr/bin/pygrub", line 545, in run_grub g = Grub(file, fs) File "/usr/bin/pygrub", line 203, in __init__ self.read_config(file, fs) File "/usr/bin/pygrub", line 402, in read_config if self.cf.filename is None: AttributeError: Grub instance has no attribute 'cf'
The error is in the parsing of the grub2 config I believe.
I've managed to setup F16 PV-guest domU under Xen Cloud Platform. It's more than just Xen, but solution will be the same. So what you need to do: 1) Don;t use GPT (install with nogpt kernel parameter) 2) Create bootable /boot partition using ext2 filesystem 3) pygrub looks for grub.cfg in /boot/grub directory (to be exact in /grub on /boot fs). But in F16 grub is located ion /boot/grub2. So I just copied grub.cfg from /boot/grub2 to /boot/grub. Maybe there is a better way to keep up-to-date copy of grub.cfg in /boot/grub. 4) pygrub bootloader fails on following line in default grub.cfg:
set default="${saved_entry}"
so I've replaced it with:
set default=0
That should be enough to make f16 to run in PV mode.
Hope it helps.
Eugene
On Tue, Jan 10, 2012 at 05:59:56PM +0400, Eugene Chupriyanov wrote:
I've managed to setup F16 PV-guest domU under Xen Cloud Platform. It's more than just Xen, but solution will be the same. So what you need to do:
- Don;t use GPT (install with nogpt kernel parameter)
- Create bootable /boot partition using ext2 filesystem
- pygrub looks for grub.cfg in /boot/grub directory (to be exact in
/grub on /boot fs). But in F16 grub is located ion /boot/grub2. So I just copied grub.cfg from /boot/grub2 to /boot/grub. Maybe there is a better way to keep up-to-date copy of grub.cfg in /boot/grub. 4) pygrub bootloader fails on following line in default grub.cfg:
set default="${saved_entry}"
so I've replaced it with:
set default=0
That should be enough to make f16 to run in PV mode.
Yes, thanks for that! This works for me. How did you know that pygrub failed on that line?
Anyway, my steps to get F16 going under Centos 5.7 with xen-3.0.3-132.el5_7.2 were:
1. Create a new PV guest and boot the F16 install image with the nogpt kernel parameter.
2. After install has finished and before you reboot, switch to text console on ALT-F2 of your install and copy the /mnt/sysimage/boot/grub2/grub.cfg to /mnt/sysimage/boot/grub/grub.cfg and edit the line:
set default="${saved_entry}"
to
set default=0
And that's it. The F16 should boot now. The only difference to Eugene's steps is that I didn't worry about the ext2 boot partition. Mine is ext4.
Also note that the copy and edit in step 2 should be easy to put in a kickstart file.
If you forget to do step 2, you can do it on the host with, in my case, kpartx, mount, and edit the files there. Remember to do a:
echo 1 > /proc/sys/vm/drop_caches
so that pygrub will read to changes and not use the cached version.
And finally, when xen-3.0.3-135 is released, it should fix this problem.
I also had success with doing an F15 install, doing an upgrade to F16 and not updating the boot loader. I then manually created a grub.cfg file. After that F16 booted OK.
I did not try R P Herrold's solution of using an F15 install, installing fedora-release-16-1.noarch.rpm with rpm, then doing a yum update.
Thanks all you your help.
I really want to thank everyone who responded!!!!
This worked for me as well and I've got it working from a kickstart installed using KOAN/Cobbler...
- After install has finished and before you reboot,
switch to text console on ALT-F2 of your install and copy the /mnt/sysimage/boot/grub2/grub.cfg to /mnt/sysimage/boot/grub/grub.cfg and edit the line:
set default="${saved_entry}"
to
set default=0
In %post, I did:
cp /boot/grub2/grub.cfg /boot/grub /bin/sed -i -e "s/set default.*/set default="0"/" /boot/grub/grub.cfg
And that's it. The F16 should boot now. The only difference to Eugene's steps is that I didn't worry about the ext2 boot partition. Mine is ext4.
I happened to use ext3 - but it worked fine...
---
Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare
On Mon, 9 Jan 2012, R P Herrold wrote:
On Tue, 10 Jan 2012, Norman Gaywood wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=746602
(pygrub cannot start F16 PV guests (GPT partition) under Xen 4.1.1)
why would one use GPT for a domU? seems like gross overkill
... following on myself, I moved a F15 box to F16 trivially just now at PMman, with grub2 in place and the full boat SELinux, running recovery backups, and so forth
I understand the desire to do native installs of domU's, but if the goal is not to test the installer, but rather to have a F16 environment to run in, F16 is readily available, and it took what? a bit under a half an hour from a standing start to all done, not even pushing hard
I'll be at Fedora's FudCon in Blacksburg this weekend, if anyone wants to stop up, say 'Hi, and try it themselves in the PMman environment, as I can clone and hand off a copy of that machine at will; I'll tear off a x64_64 box as well
-- Russ herrold
[log file is in reverse cronological sequence]
2012-01-10 04:07:09 Backup Management herrold@owlriver.com VM userbackup has been renamed: F16 post panel backup (120)
2012-01-10 04:06:36 Support Message herrold@owlriver.com Subject: post second backup herrold@2009-windows-7 ~/.ssh $ ssh -i f16 -l root 198.178.231.162 Last login: Tue Jan 10 09:04:19 2012 from cpe-75-180-54-15.columbus.res.rr.com [root@none ~]# date Tue Jan 10 09:06:17 EST 2012 [root@none ~]# T (1)
2012-01-10 04:06:01 VM State Change herrold@owlriver.com VM state has changed to Starting
2012-01-10 04:05:54 VM Management herrold@owlriver.com VM was issued a START command
2012-01-10 04:05:53 Backup Management herrold@owlriver.com VM backup is requesting the VM startup
2012-01-10 04:05:52 Backup Management herrold@owlriver.com User VM backup has completed: vm_54818_1326186306
2012-01-10 04:05:07 Backup Management herrold@owlriver.com User VM backup has been initiated: vm_54818_1326186306
2012-01-10 04:04:48 VM State Change herrold@owlriver.com VM state has changed to Stopping
2012-01-10 04:04:46 VM Management herrold@owlriver.com VM was issued a STOP command
2012-01-10 04:04:45 Backup Management herrold@owlriver.com VM backup is requesting the VM shutdown
2012-01-10 04:04:44 Backup Management herrold@owlriver.com VM backup has been ordered
2012-01-10 04:04:03 Backup Management herrold@owlriver.com VM userbackup has been renamed: F16 but pre-panel yum run (119)
2012-01-10 04:02:45 VM Management herrold@owlriver.com Yum update has been initiated on the VM: 75.180.54.15
2012-01-10 04:02:43 VM Management herrold@owlriver.com Yum was requested through the control panel: 75.180.54.15
2012-01-10 04:01:59 VM State Change herrold@owlriver.com VM state has changed to Starting
2012-01-10 04:01:52 VM Management herrold@owlriver.com VM was issued a START command
2012-01-10 04:01:51 Backup Management herrold@owlriver.com VM backup is requesting the VM startup
2012-01-10 04:01:50 Backup Management herrold@owlriver.com User VM backup has completed: vm_54818_1326185950
2012-01-10 03:59:11 Backup Management herrold@owlriver.com User VM backup has been initiated: vm_54818_1326185950
2012-01-10 03:58:52 VM State Change herrold@owlriver.com VM state has changed to Stopping
2012-01-10 03:58:50 VM Management herrold@owlriver.com VM was issued a STOP command
2012-01-10 03:58:49 Backup Management herrold@owlriver.com VM backup is requesting the VM shutdown
2012-01-10 03:58:43 Backup Management herrold@owlriver.com VM backup has been ordered
2012-01-10 03:57:56 VM Management herrold@owlriver.com VM friendly name has changed: F16 i386
2012-01-10 03:57:23 Support Message herrold@owlriver.com Subject: more of the fstab # /dev/xvda1 / ext4 defaults 1 1 /dev/xvda2 swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults T (2)
2012-01-10 03:57:03 Support Message herrold@owlriver.com Subject: fstab [root@none ~]# cat /etc/fstab
# # /etc/fstab # Created by anaconda on Sun Oct 9 21:31:47 2011 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) T (2)
2012-01-10 03:56:17 Support Message herrold@owlriver.com Subject: rest of the paste 20:10:09 UTC 2012 i686 i686 i386 GNU/Linux [root@none ~]# date Tue Jan 10 08:55:28 EST 2012 [root@none ~]# T (2)
2012-01-10 03:55:44 Support Message herrold@owlriver.com Subject: and we're back herrold@2009-windows-7 ~/.ssh $ ssh -i f16 -l root 198.178.231.162 Last login: Tue Jan 10 08:31:38 2012 from cpe-75-180-54-15.columbus.res.rr.com [root@none ~]# uname -a Linux none 3.1.7-1.fc16.i686.PAE #1 SMP Tue Jan 3 20:10: T (2)
2012-01-10 03:55:13 Support Message herrold@owlriver.com Subject: reboot delay [root@(none) ~]# reboot
(from another box, watch it)
[herrold@bronson rc.d]$ ping 198.178.231.162 PING 198.178.231.162 (198.178.231.162) 56(84) bytes of data. 64 bytes from 198.178.231.162: icmp_seq=80 ttl=64 time=1.61 ms 64 T (2)
2012-01-10 03:52:35 Support Message herrold@owlriver.com Subject: truncation issue clean all 6 yum upgrade 7 sync 8 yum clean all 9 yum upgrade 10 touch /.autorelabel 11 history [root@(none) ~]# T (2)
2012-01-10 03:52:16 Support Message herrold@owlriver.com Subject: so just before the reboot [root@(none) ~]# history 1 ifconfig 2 rpm -U http://mirror.umd.edu/fedora/linux/releases/16/Fedora/i386/os/Packages/fedor... 3 yum upgrade rpm 4 yum upgrade python 5 yu T (2)
2012-01-10 03:46:59 Support Message herrold@owlriver.com Subject: I see a bootloader replacement on the box Erasing : 1:grub-0.97-71.fc15.i686 T (2)
2012-01-10 03:45:51 Support Message herrold@owlriver.com Subject: note typo at 2012-01-10 03:33:37 this was actually: yum upgrade rpm first T (2)
2012-01-10 03:33:37 Support Message herrold@owlriver.com Subject: [root@(none) ~]# rpm -U http://mirror.umd.edu/fedora/linux/releases/16/Fedora/i386/os/Packages/fedor... warning: /var/tmp/rpm-tmp.uVjdEE: Header V3 RSA/SHA256 Signature, key ID a82ba4b7: NOKEY [root@(none) ~]# yum upgrade T (2)
2012-01-10 03:32:53 Support Message herrold@owlriver.com Subject: on the box herrold@2009-windows-7 ~ $ cd .ssh; ssh-keygen -t dsa -f f16
(inject)
herrold@2009-windows-7 ~/.ssh $ ssh -i f16 -l root 198.178.231.162 The authenticity of host '198.178.231.162 (198.178.231.162)' can't be established. RSA T (2)
2012-01-10 03:30:46 VM Management herrold@owlriver.com Initiating user requested SSH key injection [75.180.54.15]
2012-01-10 03:28:50 Support Message herrold@owlriver.com Subject: f-release is: http://mirror.umd.edu/fedora/linux/releases/16/Fedora/i386/os/Packages/fedor... T (3)
2012-01-10 03:28:03 Support Message herrold@owlriver.com Subject: migrate http://mirror.umd.edu/fedora/linux/releases/16/Fedora/i386/os/Packages/ T (3)
2012-01-10 03:26:24 VM Created herrold@owlriver.com VM XML config has been (re)created
2012-01-10 03:26:23 VM Created herrold@owlriver.com Initial cost of VM is 2000 points
2012-01-10 03:26:22 VM Created herrold@owlriver.com Configuring new VM using disk image 'Fedora 15 i386' with the following configs: vm_factor = 1, vm_mem_f = 0, vm_hd_f = 0, vm_bw_f = 0, vm_properties = para_virt,32bit,xen
On Mon, Dec 19, 2011 at 08:33:22AM -0500, Scot P. Floess wrote:
All,
I've had a heck of a time getting Fedora 16 to run as a guest VM under CentOS 5.7 host as a paravirtualized Xen guest. I believe the issue has something to do with Fedora 16 using grub2...
When I attempt to start the VM (via xm create), I get this error:
Using config file "/etc/xen/fedora-workstation". Traceback (most recent call last): File "/usr/bin/pygrub", line 686, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger "xend" Error: Boot loader didn't return any data!
Just adding the info here.. Latest Xen pygrub in centos 5.8 properly supports grub2 and Fedora 16/17 PV domUs, with and without GPT partitioned disk.
Also there's the "nogpt" boot option for Fedora 16+ installer to force it to create MSDOS partition table instead of GPT.
-- Pasi
-
Eugene Chupriyanov -
Norman Gaywood -
Pasi Kärkkäinen -
R P Herrold -
S.Tindall -
Scot P. Floess