On 07/12/2009 11:13 AM, Avi Kivity wrote:
On 07/12/2009 06:06 PM, John Rousseau wrote:
# /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
Can you try without -full-screen? Without -vga std?
Losing -vga std allowed the guest to boot.
Note -usbdevice tablet is only eating your cpu.
Cool. Removed.
Try ./configure --disable-strip.
(gdb) set args -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
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7cf5910 (LWP 2792)]
0x00000035a7c81b3b in memset () from /lib64/libc.so.6
(gdb) where
#0 0x00000035a7c81b3b in memset () from /lib64/libc.so.6
#1 0x00000000004324a1 in vbe_ioport_write_data (opaque=0x13da5e8, addr=<value optimized out>,
val=<value optimized out>) at /home/jrr/build/kvm/kvm-88/hw/vga.c:629
#2 0x000000000052873b in kvm_outw (data=<value optimized out>, addr=<value optimized out>,
opaque=<value optimized out>) at /home/jrr/build/kvm/kvm-88/qemu-kvm.c:155
#3 handle_io (data=<value optimized out>, addr=<value optimized out>, opaque=<value optimized out>)
at /home/jrr/build/kvm/kvm-88/qemu-kvm.c:877
#4 kvm_run (data=<value optimized out>, addr=<value optimized out>, opaque=<value optimized out>)
at /home/jrr/build/kvm/kvm-88/qemu-kvm.c:1103
#5 0x0000000000528873 in kvm_cpu_exec (env=0x0) at /home/jrr/build/kvm/kvm-88/qemu-kvm.c:1825
#6 0x0000000000528a16 in kvm_main_loop_cpu (env=<value optimized out>) at /home/jrr/build/kvm/kvm-88/qemu-kvm.c:2007
#7 ap_main_loop (env=<value optimized out>) at /home/jrr/build/kvm/kvm-88/qemu-kvm.c:2044
#8 0x00000035a880686a in start_thread () from /lib64/libpthread.so.0
#9 0x00000035a7cde25d in clone () from /lib64/libc.so.6
#10 0x0000000000000000 in ?? ()
Thanks
-John
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html