From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andre Przywara Subject: Re: status on broken qcow boot in ioemu-remote? Date: Thu, 31 Jul 2008 11:18:47 +0200 Message-ID: <48918377.90709@amd.com> References: <48907BB0.7020400@amd.com> <18576.35230.726763.49175@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <18576.35230.726763.49175@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 > 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