status on broken qcow boot in ioemu-remote?

status on broken qcow boot in ioemu-remote?

[Andre Przywara]

Hi,

currently in Xen unstable qcow boot support is broken if using the 
ioemu-remote tree (at least for HVM). The BIOS tells:
------------
Booting from Hard Disk...
Boot from Hard Disk failed: not a bootable disk
FATAL: No bootable device
-------------
As I saw a bug report on this yesterday on the list, I wonder if 
somebody has already started debugging on this?
It would be nice if people would share their observations on the list.

So far we can tell that it works when using the embedded ioemu and I 
vaguely remember that it worked with direct kernel boot (but currently 
cannot reproduce this) and PXE boot.

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
AMD Saxony Limited Liability Company & Co. KG,
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896, General Partner authorized
to represent: AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy

Re: status on broken qcow boot in ioemu-remote?

[Ian Jackson]

Andre Przywara writes ("status on broken qcow boot in ioemu-remote?"):
> currently in Xen unstable qcow boot support is broken if using the 
> ioemu-remote tree (at least for HVM). The BIOS tells:

Yes, there is a bug in this area.  It should be fixed in my latest
tree but that may not yet have made it out of staging.

The first commit which has all of the fix is this one:

   commit ecb9068ce70eced667eb7f0445dcb6e2506c2002
   Merge: 4f76599... ef9633e...
   Author: Ian Jackson <ian.jackson@eu.citrix.com>
   Date:   Wed Jul 30 12:07:35 2008 +0100

       Merge branch 'qemu'

Ian.

Re: status on broken qcow boot in ioemu-remote?

[Andre Przywara]

Ian Jackson wrote:
> Andre Przywara writes ("status on broken qcow boot in ioemu-remote?"):
>> currently in Xen unstable qcow boot support is broken if using the 
>> ioemu-remote tree (at least for HVM). The BIOS tells:
> 
> Yes, there is a bug in this area.  It should be fixed in my latest
> tree but that may not yet have made it out of staging.
Ah, that is a good hint. I was not aware that there is a staging tree 
for ioemu-remote. I am using the xen staging tree, shouldn't it somehow 
automatically clone the ioemu staging tree then (insert staging in the 
QEMU_REMOTE line in Config.mk)?

> The first commit which has all of the fix is this one:
> 
>    commit ecb9068ce70eced667eb7f0445dcb6e2506c2002
>    Merge: 4f76599... ef9633e...
>    Author: Ian Jackson <ian.jackson@eu.citrix.com>
>    Date:   Wed Jul 30 12:07:35 2008 +0100
> 
>        Merge branch 'qemu'
OK, this fixes the issue. Many thanks!

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917

Re: Re: status on broken qcow boot in ioemu-remote?

[Ian Jackson]

Andre Przywara writes ("[Xen-devel] Re: status on broken qcow boot in ioemu-remote?"):
> Ian Jackson wrote:
> > Yes, there is a bug in this area.  It should be fixed in my latest
> > tree but that may not yet have made it out of staging.
>
> Ah, that is a good hint. I was not aware that there is a staging tree 
> for ioemu-remote. I am using the xen staging tree, shouldn't it somehow 
> automatically clone the ioemu staging tree then (insert staging in the 
> QEMU_REMOTE line in Config.mk)?

That should work if you get the right resulting URL, yes.

> > The first commit which has all of the fix is this one:
> >    commit ecb9068ce70eced667eb7f0445dcb6e2506c2002
...
> OK, this fixes the issue. Many thanks!

Excellent.

Thanks,
Ian.