public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: John Rousseau <jrrousseau@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] kvm-88 release
Date: Sun, 12 Jul 2009 11:06:26 -0400	[thread overview]
Message-ID: <4A59FBF2.2050904@gmail.com> (raw)
In-Reply-To: <4A59E599.4080802@redhat.com>

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

  reply	other threads:[~2009-07-12 15:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12 13:31 [ANNOUNCE] kvm-88 release Avi Kivity
2009-07-12 15:06 ` John Rousseau [this message]
2009-07-12 15:13   ` Avi Kivity
2009-07-12 18:43     ` John Rousseau
2009-07-13  8:32       ` Avi Kivity
2009-07-13 11:27         ` John Rousseau
2009-07-13  8:40     ` Michael Tokarev
2009-07-13  9:08       ` Avi Kivity
2009-07-13 10:01         ` Erik Rull
2009-07-13 11:20           ` Avi Kivity
2009-07-13 15:00           ` Anthony Liguori
2009-07-12 16:01 ` [ANNOUNCE] kvm-88 release (CAN NOT install modules on debian/amd64/2.6.30) John Wong
2009-07-12 17:45   ` Avi Kivity
2009-07-17 23:59   ` Marcelo Tosatti
2009-07-19  3:41     ` John Wong
2009-07-20 14:42       ` Marcelo Tosatti
2009-07-20 17:05         ` John Wong

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=4A59FBF2.2050904@gmail.com \
    --to=jrrousseau@gmail.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox