On 06/15/2011 06:27 PM, Jason Krieg wrote:
On 06/15/2011 05:19 PM, Avi Kivity wrote:
On 06/15/2011 06:16 PM, Jason Krieg wrote:
On 06/15/2011 03:59 PM, Avi Kivity wrote:
On 06/15/2011 04:57 PM, Avi Kivity wrote:
Any ideas for what I could look for ?
Try -no-tpr-opt (on both sides).
T
On 06/15/2011 05:19 PM, Avi Kivity wrote:
On 06/15/2011 06:16 PM, Jason Krieg wrote:
On 06/15/2011 03:59 PM, Avi Kivity wrote:
On 06/15/2011 04:57 PM, Avi Kivity wrote:
Any ideas for what I could look for ?
Try -no-tpr-opt (on both sides).
There's no such option. Try commenting out t
On 06/15/2011 06:16 PM, Jason Krieg wrote:
On 06/15/2011 03:59 PM, Avi Kivity wrote:
On 06/15/2011 04:57 PM, Avi Kivity wrote:
Any ideas for what I could look for ?
Try -no-tpr-opt (on both sides).
There's no such option. Try commenting out the device_init line of
kvm-tpr-opt.c.
On 06/15/2011 03:59 PM, Avi Kivity wrote:
On 06/15/2011 04:57 PM, Avi Kivity wrote:
Any ideas for what I could look for ?
Try -no-tpr-opt (on both sides).
There's no such option. Try commenting out the device_init line of
kvm-tpr-opt.c.
I disabled this on both sides but still the
On 06/15/2011 04:11 PM, Jason Krieg wrote:
On 06/15/2011 03:59 PM, Avi Kivity wrote:
On 06/15/2011 04:57 PM, Avi Kivity wrote:
Any ideas for what I could look for ?
Try -no-tpr-opt (on both sides).
There's no such option. Try commenting out the device_init line of
kvm-tpr-opt.c.
On 06/15/2011 03:59 PM, Avi Kivity wrote:
On 06/15/2011 04:57 PM, Avi Kivity wrote:
Any ideas for what I could look for ?
Try -no-tpr-opt (on both sides).
There's no such option. Try commenting out the device_init line of
kvm-tpr-opt.c.
with 0.12.5 there is no device_init in kvm-t
On 06/15/2011 04:57 PM, Avi Kivity wrote:
Any ideas for what I could look for ?
Try -no-tpr-opt (on both sides).
There's no such option. Try commenting out the device_init line of
kvm-tpr-opt.c.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from th
On 06/15/2011 04:54 PM, Jason Krieg wrote:
Maybe instead of reverting this commit one could check the seabios
version in this method
and only do an update of these piix PAM registers if running with a
newer seabios version ?
It would be better to first understand what's going wrong.
I
On 06/15/2011 03:17 PM, Avi Kivity wrote:
On 06/15/2011 02:58 PM, Jason Krieg wrote:
On 09/21/2010 02:31 PM, Gleb Natapov wrote:
Without this BIOS fails to remap 0xf memory from ROM to RAM so
writes
to F-segment modify ROM content instead of memory copy. Since QEMU does
not reloads ROMs du
On 06/15/2011 02:58 PM, Jason Krieg wrote:
On 09/21/2010 02:31 PM, Gleb Natapov wrote:
Without this BIOS fails to remap 0xf memory from ROM to RAM so
writes
to F-segment modify ROM content instead of memory copy. Since QEMU does
not reloads ROMs during reset on next boot modified copy of BI
On 09/21/2010 02:31 PM, Gleb Natapov wrote:
Without this BIOS fails to remap 0xf memory from ROM to RAM so writes
to F-segment modify ROM content instead of memory copy. Since QEMU does
not reloads ROMs during reset on next boot modified copy of BIOS is used.
Signed-off-by: Gleb Natapov
diff
On Tue, Sep 21, 2010 at 04:06:01PM -0300, Marcelo Tosatti wrote:
> On Tue, Sep 21, 2010 at 02:31:42PM +0200, Gleb Natapov wrote:
> > Without this BIOS fails to remap 0xf memory from ROM to RAM so writes
> > to F-segment modify ROM content instead of memory copy. Since QEMU does
> > not reloads
On Tue, Sep 21, 2010 at 02:31:42PM +0200, Gleb Natapov wrote:
> Without this BIOS fails to remap 0xf memory from ROM to RAM so writes
> to F-segment modify ROM content instead of memory copy. Since QEMU does
> not reloads ROMs during reset on next boot modified copy of BIOS is used.
>
> Signed
Without this BIOS fails to remap 0xf memory from ROM to RAM so writes
to F-segment modify ROM content instead of memory copy. Since QEMU does
not reloads ROMs during reset on next boot modified copy of BIOS is used.
Signed-off-by: Gleb Natapov
diff --git a/hw/piix_pci.c b/hw/piix_pci.c
index
14 matches
Mail list logo