qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] insmod virtio-blk is broken in qemu 1.0


From: Anthony Liguori
Subject: Re: [Qemu-devel] insmod virtio-blk is broken in qemu 1.0
Date: Sat, 17 Dec 2011 11:03:45 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13

On 12/17/2011 10:49 AM, Kevin O'Connor wrote:
On Sat, Dec 17, 2011 at 10:24:07AM -0600, Anthony Liguori wrote:
On 12/17/2011 09:25 AM, Richard W.M. Jones wrote:
On Sat, Dec 17, 2011 at 09:22:45AM -0600, Anthony Liguori wrote:
I've even further narrowed it down to the presents or lack of '-vga
cirrus'.  If you add '-vga cirrus' to the above command line, the
guest will boot successfully.

Confirmed: Adding -vga cirrus to the command line cures it too.

That's a strange one :-)

vga sticks out a bit because it's one of the few places where we
treat device memory as ram as a performance optimization.

The only time vga has been touched in between v0.15 and v1.0 was
during the introduction of the memory API.

It's this commit:

commit d67c3f2cd92aed2247bfa8a9da61a902b7b2ff09
Author: Gerd Hoffmann<address@hidden>
Date:   Wed Aug 10 17:34:13 2011 +0200

     seabios: update to master

This looks like the same issue reported at:

http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg00029.html

The SeaBIOS fix for this was in rel-1.6.3.1 - but that didn't make
QEmu 1.0.  Does the problem go away if you upgrade to the newer
SeaBIOS version?

Er, I can't actually build SeaBIOS anymore...

The version of LD on this system does not properly handle
alignments.  As a result, this project can not be built.

The problem may be the result of this LD bug report:
 http://sourceware.org/bugzilla/show_bug.cgi?id=12726

Please update to a working version of binutils and retry.
Makefile:75: *** "Please upgrade GCC and/or binutils".  Stop.

Let me find a box with a newer binutils...

Regards,

Anthony Liguori


-Kevin





reply via email to

[Prev in Thread] Current Thread [Next in Thread]