Description of problem: Booting a snv_114 domU with pygrub: Error: Boot loader didn't return any data! Version-Release number of selected component (if applicable): xen-3.3.1-11 Additional info: The zfs on-disk format changed with snv_114. The following changesets should allow booting with pygrub: http://xenbits.xensource.com/xen-unstable.hg?rev/40e8684a34bf http://xenbits.xensource.com/xen-unstable.hg?rev/3118041f2259
Already working on xen 3.4.0 update for rawhide (aka f12). Dunno what to do best about f11. Given that xen in f11 is very experimental anyway (needs a third-party kernel for starters ...) I tend to jump to 3.4 as well instead of cherry-picking more patches.
(In reply to comment #1) > Dunno what to do best about f11. Given that xen in f11 is very experimental > anyway (needs a third-party kernel for starters ...) I tend to jump to 3.4 as > well instead of cherry-picking more patches. FWIW, that sounds reasonable to me - anyone using f11 as a dom0 surely can't be demanding complete stability
I totally agree, and will wait for xen 3.4. Thanks.
http://kojipkgs.fedoraproject.org/packages/xen/3.4.0/1.fc12/
Thanks, I'll check them out! One issue though: [ruben@fikkie ~]$ sudo rpm -Uvh xen-*.rpm Preparing... ########################################### [100%] file /usr/share/info/configure.info.gz from install of xen-doc-3.4.0-1.fc12.x86_64 conflicts with file from package binutils-2.19.51.0.2-17.fc11.x86_64 file /usr/share/info/standards.info.gz from install of xen-doc-3.4.0-1.fc12.x86_64 conflicts with file from package binutils-2.19.51.0.2-17.fc11.x86_64
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Thanks to the backports, I was able to install snv_123 successfully with xen-3.4.1-4. It even works with pygrub.