kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: Reconciling qemu-kvm and qemu's PIT
Date: Tue, 28 Feb 2012 21:50:05 +0200	[thread overview]
Message-ID: <4F4D2FED.1030207@redhat.com> (raw)
In-Reply-To: <4F4CE7CB.8090409@redhat.com>

On 02/28/2012 04:42 PM, Avi Kivity wrote:

<snip>

I'm getting a crash now:

#0  0x00007ffff4ea0285 in raise    () from /lib64/libc.so.6
#1  0x00007ffff4ea1b9b in abort    () from /lib64/libc.so.6
#2  0x00007ffff4e98e9e in __assert_fail_base ()    from /lib64/libc.so.6
#3  0x00007ffff4e98f42 in __assert_fail    () from /lib64/libc.so.6
#4  0x000055555571c69b in qdev_connect_gpio_out    (dev=0x555556913a70,
n=0, pin=0x5555568ef770) at /home/tlv/akivity/qemu/hw/qdev.c:297
#5  0x000055555582beae in pit_init (bus=0x5555568d5610,    base=64,
isa_irq=-1, alt_irq=0x5555568ef770) at /home/tlv/akivity/qemu/hw/i8254.h:85
#6  0x000055555582ebbc in pc_basic_device_init
(isa_bus=0x5555568d5610,    gsi=0x5555568cadb0,
rtc_state=0x7fffffffdea0, floppy=0x7fffffffdea8, no_vmport=false)
    at /home/tlv/akivity/qemu/hw/pc.c:1182
#7  0x000055555582f454 in pc_init1 (system_memory=0x55555646f270,
system_io=0x55555646f360, ram_size=1073741824,
boot_device=0x7fffffffe300 "cad", kernel_filename=0x0,   
    kernel_cmdline=0x5555558baa12 "", initrd_filename=0x0,
cpu_model=0x0, pci_enabled=1, kvmclock_enabled=1) at
/home/tlv/akivity/qemu/hw/pc_piix.c:256
#8  0x000055555582f8d7 in pc_init_pci (ram_size=1073741824,
boot_device=0x7fffffffe300 "cad", kernel_filename=0x0,
kernel_cmdline=0x5555558baa12 "", initrd_filename=0x0,
    cpu_model=0x0) at /home/tlv/akivity/qemu/hw/pc_piix.c:335
#9  0x00005555556f1349 in main (argc=6,    argv=0x7fffffffe428,
envp=0x7fffffffe460) at /home/tlv/akivity/qemu/vl.c:3431

Looks like isa-pit has zero gpio pins, so it fails when crashing.  I
must have mismerged it, but where is the gpio pin count set?


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2012-02-28 19:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 14:32 Reconciling qemu-kvm and qemu's PIT Avi Kivity
2012-02-28 14:40 ` Jan Kiszka
2012-02-28 14:42   ` Avi Kivity
2012-02-28 19:50     ` Avi Kivity [this message]
2012-02-28 21:47       ` Jan Kiszka
2012-02-29  9:29         ` Avi Kivity
2012-02-29 10:14           ` Jan Kiszka
2012-02-29 13:45             ` Avi Kivity
2012-02-29 14:24               ` Jan Kiszka
2012-02-29 14:42                 ` Avi Kivity

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=4F4D2FED.1030207@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@siemens.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;
as well as URLs for NNTP newsgroup(s).