Re: Reconciling qemu-kvm and qemu's PIT

2012-02-29 Thread Avi Kivity
On 02/29/2012 04:24 PM, Jan Kiszka wrote: > On 2012-02-29 14:45, Avi Kivity wrote: > > On 02/29/2012 12:14 PM, Jan Kiszka wrote: > >> On 2012-02-29 10:29, Avi Kivity wrote: > >>> On 02/28/2012 11:47 PM, Jan Kiszka wrote: > > > > Looks like isa-pit has zero gpio pins, so it fails when crashi

Re: Reconciling qemu-kvm and qemu's PIT

2012-02-29 Thread Jan Kiszka
On 2012-02-29 14:45, Avi Kivity wrote: > On 02/29/2012 12:14 PM, Jan Kiszka wrote: >> On 2012-02-29 10:29, Avi Kivity wrote: >>> On 02/28/2012 11:47 PM, Jan Kiszka wrote: > > Looks like isa-pit has zero gpio pins, so it fails when crashing. I > must have mismerged it, but where is the

Re: Reconciling qemu-kvm and qemu's PIT

2012-02-29 Thread Avi Kivity
On 02/29/2012 12:14 PM, Jan Kiszka wrote: > On 2012-02-29 10:29, Avi Kivity wrote: > > On 02/28/2012 11:47 PM, Jan Kiszka wrote: > >>> > >>> 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? > >> > >> In pit_initf

Re: Reconciling qemu-kvm and qemu's PIT

2012-02-29 Thread Jan Kiszka
On 2012-02-29 10:29, Avi Kivity wrote: > On 02/28/2012 11:47 PM, Jan Kiszka wrote: >>> >>> 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? >> >> In pit_initfn. Does -no-kvm-irqchip work fine? It's a bit tricky to

Re: Reconciling qemu-kvm and qemu's PIT

2012-02-29 Thread Avi Kivity
On 02/28/2012 11:47 PM, Jan Kiszka wrote: > > > > 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? > > In pit_initfn. Does -no-kvm-irqchip work fine? It's a bit tricky to > discuss this without seeing your code. >

Re: Reconciling qemu-kvm and qemu's PIT

2012-02-28 Thread Jan Kiszka
On 2012-02-28 20:50, Avi Kivity wrote: > On 02/28/2012 04:42 PM, Avi Kivity wrote: > > > > I'm getting a crash now: > > #0 0x74ea0285 in raise() from /lib64/libc.so.6 > #1 0x74ea1b9b in abort() from /lib64/libc.so.6 > #2 0x74e98e9e in __assert_fail_base ()

Re: Reconciling qemu-kvm and qemu's PIT

2012-02-28 Thread Avi Kivity
On 02/28/2012 04:42 PM, Avi Kivity wrote: I'm getting a crash now: #0 0x74ea0285 in raise() from /lib64/libc.so.6 #1 0x74ea1b9b in abort() from /lib64/libc.so.6 #2 0x74e98e9e in __assert_fail_base ()from /lib64/libc.so.6 #3 0x74e98f42 in __assert_

Re: Reconciling qemu-kvm and qemu's PIT

2012-02-28 Thread Avi Kivity
On 02/28/2012 04:40 PM, Jan Kiszka wrote: > On 2012-02-28 15:32, Avi Kivity wrote: > > > > VMStateDescription vmstate_pit = { > > .name = "i8254", > > .version_id = 3, > > .minimum_version_id = 2, > > .minimum_version_id_old = 1, > > .load_state_old = pit_load_old, > > .fie

Re: Reconciling qemu-kvm and qemu's PIT

2012-02-28 Thread Jan Kiszka
On 2012-02-28 15:32, Avi Kivity wrote: > > VMStateDescription vmstate_pit = { > .name = "i8254", > .version_id = 3, > .minimum_version_id = 2, > .minimum_version_id_old = 1, > .load_state_old = pit_load_old, > .fields = (VMStateField []) { > <<< HEAD > VMST