Re: [Xen-users] How to get pygrub to load grub2 guest on Squeeze Dom0.

[Kyle Lexmond <kyl191@xxxxxxxxxx>]

I had a similar problem with my F16 PV install that came down to
having /boot formatted as btrfs - except pygrub doesn't support it, so
it can't read the initrd & kernel. I can't remember it btrfs was the
default filesystem for /boot though, and even if it is, you might have
changed it to ext3/4, so this might not help.

If this is your problem, how I fixed it:
I ended up creating a new LV, formatting it as ext4, block-attaching
both the btrfs and ext4 formatted LVs to my dom0, and copying the grub
files from the btrfs LV to the ext4 LV.

One point if you do this: The new LV has a different UUID though, so
F16 refused to boot because the disks are referenced by UUID in the
domU's /etc/fstab, so you'll need to change that.  I resorted to doing
it all through the emergency shell, taking advantage of screen's text
buffer to copy the output.

I documented what I did here -
http://kyl191.net/2011/10/stupid-trick-changing-the-uuid-in-etcfstab-from-an-emergency-shell-with-screen/
if you're inclined to follow it, but because it took a fair bit of
unnecessary configuration, I recommend running blkid in your dom0 and
replacing the UUID in your domU's /etc/fstab after attaching the
domU's root partition to your dom0, and editing with
$EDITOR_OF_CHOICE.

Hope that helped, and good luck.

On Tue, Nov 15, 2011 at 8:18 AM, Bud Bundy <budric@xxxxxxxxx> wrote:
> Hi,
> I'm trying to install a FC 16 PV guest. ÂAfter installation the guest
> doesn't load with:ÂError: Boot loader didn't return any data!
> xend.log:
> [2011-11-14 18:57:32 32321] ERROR (XendBootloader:214) Boot loader didn't
> return any data!
> [2011-11-14 18:57:32 32321] ERROR (XendDomainInfo:483) VM start failed
> Traceback (most recent call last):
> Â File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 469,
> in start
> Â Â XendTask.log_progress(31, 60, self._initDomain)
> Â File "/usr/lib/xen-4.0/lib/python/xen/xend/XendTask.py", line 209, in
> log_progress
> Â Â retval = func(*args, **kwds)
> Â File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 2820,
> in _initDomain
> Â Â self._configureBootloader()
> Â File "/usr/lib/xen-4.0/lib/python/xen/xend/XendDomainInfo.py", line 3266,
> in _configureBootloader
> Â Â bootloader_args, kernel, ramdisk, args)
> Â File "/usr/lib/xen-4.0/lib/python/xen/xend/XendBootloader.py", line 215,
> in bootloader
> Â Â raise VmError, msg
> The only thing I could find that was close is this:
> Reading the wiki this is a known
> issue:Âhttp://wiki.debian.org/Xen#Upgrading.2BAC8-transition
> With a bug report in
> debian:Âhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599243
> If I'm reading bug report correctly it's fixed in 4.0.1-2?
> When I do apt-cache show xen-hypervisor-4.0-amd64, the version I have is
> 4.0.1-4.
> Thanks
> _______________________________________________
> 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