All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: status on broken qcow boot in ioemu-remote?
Date: Thu, 31 Jul 2008 11:18:47 +0200	[thread overview]
Message-ID: <48918377.90709@amd.com> (raw)
In-Reply-To: <18576.35230.726763.49175@mariner.uk.xensource.com>

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

  reply	other threads:[~2008-07-31  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 14:33 status on broken qcow boot in ioemu-remote? Andre Przywara
2008-07-30 15:32 ` Ian Jackson
2008-07-31  9:18   ` Andre Przywara [this message]
2008-07-31  9:44     ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48918377.90709@amd.com \
    --to=andre.przywara@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.