Re: [Qemu-devel] Win2k broken by kvmvapic

2012-10-07 Thread Jan Kiszka
On 2012-10-07 20:40, Blue Swirl wrote: > On Sun, Oct 7, 2012 at 5:24 PM, Jan Kiszka wrote: >> On 2012-10-07 17:23, Blue Swirl wrote: >>> Hi, >>> >>> Win2k does not work in HEAD, it resets the machine. I bisected this to >>> 0b57e287138728f72d88b06e69b970c5d745c44a, but that does not look so >>> bu

Re: [Qemu-devel] Win2k broken by kvmvapic

2012-10-07 Thread Blue Swirl
On Sun, Oct 7, 2012 at 5:24 PM, Jan Kiszka wrote: > On 2012-10-07 17:23, Blue Swirl wrote: >> Hi, >> >> Win2k does not work in HEAD, it resets the machine. I bisected this to >> 0b57e287138728f72d88b06e69b970c5d745c44a, but that does not look so >> buggy. >> >> Digging deeper, the problem is intro

Re: [Qemu-devel] Win2k broken by kvmvapic

2012-10-07 Thread Jan Kiszka
On 2012-10-07 17:23, Blue Swirl wrote: > Hi, > > Win2k does not work in HEAD, it resets the machine. I bisected this to > 0b57e287138728f72d88b06e69b970c5d745c44a, but that does not look so > buggy. > > Digging deeper, the problem is introduced by kvmvapic: > Breakpoint 1, cpu_physical_memory_wri

[Qemu-devel] Win2k broken by kvmvapic

2012-10-07 Thread Blue Swirl
Hi, Win2k does not work in HEAD, it resets the machine. I bisected this to 0b57e287138728f72d88b06e69b970c5d745c44a, but that does not look so buggy. Digging deeper, the problem is introduced by kvmvapic: Breakpoint 1, cpu_physical_memory_write_rom (addr=0xca300, buf=0x7fffec66b500 "", len=0x