From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Rousseau <jrrousseau@gmail.com>
Subject: Re: [ANNOUNCE] kvm-88 release
Date: Sun, 12 Jul 2009 11:06:26 -0400
Message-ID: <4A59FBF2.2050904@gmail.com>
References: <4A59E599.4080802@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: KVM list <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from qw-out-2122.google.com ([74.125.92.25]:43548 "EHLO
	qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753912AbZGLPM2 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 12 Jul 2009 11:12:28 -0400
Received: by qw-out-2122.google.com with SMTP id 9so661048qwb.37
        for <kvm@vger.kernel.org>; Sun, 12 Jul 2009 08:12:27 -0700 (PDT)
In-Reply-To: <4A59E599.4080802@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 07/12/2009 09:31 AM, Avi Kivity wrote:
> kvm-87 wasn't so hot due to networking not working with rtl8139 and
> e1000.  So kvm-88 fixes that and brings a bunch of new features
> (resizable sdl windows, multiboot, x2apic, and more). Enjoy.

Does anyone have this working with FC11?

I installed FC11 on a new laptop, replacing my old FC9-running laptop 
last week and I have been unable to run my Vista guest since:

> # /usr/local/bin/qemu-system-x86_64 -hda /home/jrr/vista-x86_64.img -m 1536M -net nic,vlan=0,macaddr=52:54:00:12:32:00 -net tap,vlan=0,ifname=tap1 -vga std -full-screen -smp 2 -usb -usbdevice tablet
> Executing /etc/qemu-ifup
> Bringing up tap1 for bridged mode...
> Adding tap1 to br0...
> Bad ram offset 60909fff
> Aborted

I've been running this guest since ~kvm-75 on FC9. Dropping the smp, usb 
and full-screen options doesn't help. The crash is after the cylon 
Windows startup bar but before the login screen.

Host is FC11 x86_64, 2.6.29.4-167.fc11.x86_64. Intel P8700. 4GB memory.
Guest is Vista Ultimate 64.

An added bonus is that the crash leaves Xorg in 640x480 resolution. I've 
also seen just a seg fault instead of the "Bad ram" error.

gdb reports the following if this is at all helpful:

> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ffff7cf5910 (LWP 3577)]
> 0x00000035a7c81b3b in memset () from /lib64/libc.so.6
> (gdb) where
> #0  0x00000035a7c81b3b in memset () from /lib64/libc.so.6
> #1  0x00000000004324a1 in pthread_attr_setdetachstate ()
> #2  0x000000000052873b in pthread_attr_setdetachstate ()
> #3  0x0000000000528873 in pthread_attr_setdetachstate ()
> #4  0x0000000000528a16 in pthread_attr_setdetachstate ()
> #5  0x00000035a880686a in start_thread () from /lib64/libpthread.so.0
> #6  0x00000035a7cde25d in clone () from /lib64/libc.so.6
> #7  0x0000000000000000 in ?? ()
> (gdb) info threads
>   3 Thread 0x7ffff683a910 (LWP 3578)  0x00000035a880e778 in pread64 () from /lib64/libpthread.so.0
> * 2 Thread 0x7ffff7cf5910 (LWP 3577)  0x00000035a7c81b3b in memset () from /lib64/libc.so.6
>   1 Thread 0x7ffff7d4a6f0 (LWP 3564)  0x00000035a880d934 in __lll_lock_wait () from /lib64/libpthread.so.0

Thanks
-John