From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@SIEMENS.COM>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15
Date: Tue, 06 Dec 2011 23:38:25 +0400 [thread overview]
Message-ID: <4EDE6F31.7090706@msgid.tls.msk.ru> (raw)
In-Reply-To: <4EDE62C6.8000506@msgid.tls.msk.ru>
[Removed some people from the Cc list]
On 06.12.2011 22:45, Michael Tokarev wrote:
[]
>> git://git.kiszka.org/qemu-kvm.git queues/kvm-irqchip
>
> This tree does not boot for me at all (on regular x86-64 setup) -
> it stays in bios after "Booting from hard disk" with 100% CPU
> usage.
This happens since
commit 1ae1cec76a205446e6b4e5600ad0af450f7c0b5e
Author: Jan Kiszka <jan.kiszka@siemens.com>
Date: Sun Oct 16 19:38:22 2011 +0200
ioapic: Introduce backend/frontend infrastructure for KVM reuse
Also, with this
commit 063e1bea9b0c79bda48c9e82552c5c6c83d03cf7
Author: Jan Kiszka <jan.kiszka@siemens.com>
Date: Sat Oct 15 11:49:47 2011 +0200
kvm: Introduce core services for in-kernel irqchip support
the whole thing segfaults at startup:
(gdb) ru -monitor stdio -m 1G -netdev type=tap,ifname=tap-kvm1,script=no,downscript=no,id=n -device rtl8139,netdev=n,mac=52:54:00:12:34:57 -drive file=/stage/win/dist/t.raw,if=ide,cache=unsafe -vga std -usbdevice tablet -enable-kvm
...
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5670c7a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x00007ffff5670c7a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00005555557abb3d in ioapic_init (dev=0x555556849f60)
at /build/kvm/git/hw/ioapic_common.c:92
#2 0x00005555556a0a85 in sysbus_device_init (dev=0x555556849f60,
base=0x555555be7200) at /build/kvm/git/hw/sysbus.c:133
#3 0x00005555556df670 in qdev_init (dev=0x555556849f60)
at /build/kvm/git/hw/qdev.c:293
#4 0x00005555556dfa8a in qdev_init_nofail (dev=0x555556849f60)
at /build/kvm/git/hw/qdev.c:387
#5 0x00005555557f9bc2 in ioapic_init (gsi_state=0x55555683ff70)
at /build/kvm/git/hw/pc_piix.c:63
#6 0x00005555557f9f76 in pc_init1 (system_memory=0x55555641a1b0,
system_io=0x55555641a2b0, ram_size=1073741824,
boot_device=0x7fffffffea30 "cad", kernel_filename=0x0,
kernel_cmdline=0x55555586fbff "", initrd_filename=0x0, cpu_model=0x0,
pci_enabled=1, kvmclock_enabled=1) at /build/kvm/git/hw/pc_piix.c:166
#7 0x00005555557fa425 in pc_init_pci (ram_size=1073741824,
boot_device=0x7fffffffea30 "cad", kernel_filename=0x0,
kernel_cmdline=0x55555586fbff "", initrd_filename=0x0, cpu_model=0x0)
at /build/kvm/git/hw/pc_piix.c:245
#8 0x00005555556b99ca in main (argc=16, argv=0x7fffffffeb58,
envp=0x7fffffffebe0) at /build/kvm/git/vl.c:3351
(gdb) frame 1
#1 0x00005555557abb3d in ioapic_init (dev=0x555556849f60)
at /build/kvm/git/hw/ioapic_common.c:92
92 if (strcmp(b->name, s->backend_name) == 0) {
(gdb) p b->name
$1 = 0x55555588588d "QEMU"
(gdb) p s->backend_name
$2 = 0x0
(gdb) _
Thanks!
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@SIEMENS.COM>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] winXP "Standard PC" HAL and qemu-kvm >= 0.15
Date: Tue, 06 Dec 2011 23:38:25 +0400 [thread overview]
Message-ID: <4EDE6F31.7090706@msgid.tls.msk.ru> (raw)
In-Reply-To: <4EDE62C6.8000506@msgid.tls.msk.ru>
[Removed some people from the Cc list]
On 06.12.2011 22:45, Michael Tokarev wrote:
[]
>> git://git.kiszka.org/qemu-kvm.git queues/kvm-irqchip
>
> This tree does not boot for me at all (on regular x86-64 setup) -
> it stays in bios after "Booting from hard disk" with 100% CPU
> usage.
This happens since
commit 1ae1cec76a205446e6b4e5600ad0af450f7c0b5e
Author: Jan Kiszka <jan.kiszka@siemens.com>
Date: Sun Oct 16 19:38:22 2011 +0200
ioapic: Introduce backend/frontend infrastructure for KVM reuse
Also, with this
commit 063e1bea9b0c79bda48c9e82552c5c6c83d03cf7
Author: Jan Kiszka <jan.kiszka@siemens.com>
Date: Sat Oct 15 11:49:47 2011 +0200
kvm: Introduce core services for in-kernel irqchip support
the whole thing segfaults at startup:
(gdb) ru -monitor stdio -m 1G -netdev type=tap,ifname=tap-kvm1,script=no,downscript=no,id=n -device rtl8139,netdev=n,mac=52:54:00:12:34:57 -drive file=/stage/win/dist/t.raw,if=ide,cache=unsafe -vga std -usbdevice tablet -enable-kvm
...
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5670c7a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x00007ffff5670c7a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00005555557abb3d in ioapic_init (dev=0x555556849f60)
at /build/kvm/git/hw/ioapic_common.c:92
#2 0x00005555556a0a85 in sysbus_device_init (dev=0x555556849f60,
base=0x555555be7200) at /build/kvm/git/hw/sysbus.c:133
#3 0x00005555556df670 in qdev_init (dev=0x555556849f60)
at /build/kvm/git/hw/qdev.c:293
#4 0x00005555556dfa8a in qdev_init_nofail (dev=0x555556849f60)
at /build/kvm/git/hw/qdev.c:387
#5 0x00005555557f9bc2 in ioapic_init (gsi_state=0x55555683ff70)
at /build/kvm/git/hw/pc_piix.c:63
#6 0x00005555557f9f76 in pc_init1 (system_memory=0x55555641a1b0,
system_io=0x55555641a2b0, ram_size=1073741824,
boot_device=0x7fffffffea30 "cad", kernel_filename=0x0,
kernel_cmdline=0x55555586fbff "", initrd_filename=0x0, cpu_model=0x0,
pci_enabled=1, kvmclock_enabled=1) at /build/kvm/git/hw/pc_piix.c:166
#7 0x00005555557fa425 in pc_init_pci (ram_size=1073741824,
boot_device=0x7fffffffea30 "cad", kernel_filename=0x0,
kernel_cmdline=0x55555586fbff "", initrd_filename=0x0, cpu_model=0x0)
at /build/kvm/git/hw/pc_piix.c:245
#8 0x00005555556b99ca in main (argc=16, argv=0x7fffffffeb58,
envp=0x7fffffffebe0) at /build/kvm/git/vl.c:3351
(gdb) frame 1
#1 0x00005555557abb3d in ioapic_init (dev=0x555556849f60)
at /build/kvm/git/hw/ioapic_common.c:92
92 if (strcmp(b->name, s->backend_name) == 0) {
(gdb) p b->name
$1 = 0x55555588588d "QEMU"
(gdb) p s->backend_name
$2 = 0x0
(gdb) _
Thanks!
/mjt
next prev parent reply other threads:[~2011-12-06 19:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 9:21 winXP "Standard PC" HAL and qemu-kvm >= 0.15 Michael Tokarev
2011-12-05 13:28 ` Avi Kivity
2011-12-05 20:19 ` Michael Tokarev
2011-12-06 10:32 ` Avi Kivity
2011-12-06 11:02 ` Michael Tokarev
2011-12-06 12:27 ` Michael S. Tsirkin
2011-12-06 12:27 ` [Qemu-devel] " Michael S. Tsirkin
2011-12-06 14:45 ` Michael Tokarev
2011-12-06 14:45 ` [Qemu-devel] " Michael Tokarev
2011-12-06 16:29 ` Michael Tokarev
2011-12-06 16:29 ` Michael Tokarev
2011-12-06 16:38 ` Jan Kiszka
2011-12-06 16:38 ` [Qemu-devel] " Jan Kiszka
2011-12-06 16:57 ` Michael Tokarev
2011-12-06 16:57 ` [Qemu-devel] " Michael Tokarev
2011-12-06 17:45 ` Jan Kiszka
2011-12-06 17:45 ` [Qemu-devel] " Jan Kiszka
2011-12-06 18:13 ` Michael Tokarev
2011-12-06 18:13 ` [Qemu-devel] " Michael Tokarev
2011-12-06 18:21 ` Jan Kiszka
2011-12-06 18:21 ` [Qemu-devel] " Jan Kiszka
2011-12-06 18:45 ` Michael Tokarev
2011-12-06 18:45 ` [Qemu-devel] " Michael Tokarev
2011-12-06 19:38 ` Michael Tokarev [this message]
2011-12-06 19:38 ` Michael Tokarev
2011-12-06 20:58 ` Jan Kiszka
2011-12-06 20:58 ` [Qemu-devel] " Jan Kiszka
2011-12-06 21:12 ` Jan Kiszka
2011-12-06 21:12 ` [Qemu-devel] " Jan Kiszka
2011-12-07 7:11 ` Michael Tokarev
2011-12-07 9:02 ` Kevin Wolf
2011-12-07 9:02 ` [Qemu-devel] " Kevin Wolf
2011-12-07 9:31 ` Michael Tokarev
2011-12-07 9:31 ` Michael Tokarev
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=4EDE6F31.7090706@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jan.kiszka@SIEMENS.COM \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.