On 07.05.2012 22:07, Jan Kiszka wrote:
> On 2012-05-07 14:48, Michael Tokarev wrote:
>> On 07.05.2012 19:32, Jan Kiszka wrote:
>>> On 2012-05-07 11:45, Michael Tokarev wrote:
>> []
$ ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -drive
file=w7x32sp1.raw,if=virtio,snapshot=on -m 1G -net
On 2012-05-07 14:48, Michael Tokarev wrote:
> On 07.05.2012 19:32, Jan Kiszka wrote:
>> On 2012-05-07 11:45, Michael Tokarev wrote:
> []
>>> $ ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -drive
>>> file=w7x32sp1.raw,if=virtio,snapshot=on -m 1G -net none -machine
>>> accel=kvm,kernel_irqchip=o
On 07.05.2012 19:32, Jan Kiszka wrote:
> On 2012-05-07 11:45, Michael Tokarev wrote:
[]
>> $ ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -drive
>> file=w7x32sp1.raw,if=virtio,snapshot=on -m 1G -net none -machine
>> accel=kvm,kernel_irqchip=on
>
> Can you check if -global apic.vapic=off makes
On 05/07/2012 04:51 PM, Michael Tokarev wrote:
> So, refreshing it all again with more correct information.
>
> First, it appears that only 32bit version of qemu userspace is
> affected, and only when using 32bit version of guest. So far,
> either 64bit qemu userpace or 64bit windows7 guest is eno
On 2012-05-07 11:45, Michael Tokarev wrote:
> On 07.05.2012 18:35, Michael Tokarev wrote:
>> On 07.05.2012 18:18, Jan Kiszka wrote:
>> []
>>> I have a 32-bit WinXP here to test (but not a Win7-32) and will give it
>>
>> I just found out that a 32bit guest is not enough. The problem appears
>> to b
On 07.05.2012 18:35, Michael Tokarev wrote:
> On 07.05.2012 18:18, Jan Kiszka wrote:
> []
>> I have a 32-bit WinXP here to test (but not a Win7-32) and will give it
>
> I just found out that a 32bit guest is not enough. The problem appears
> to be with 32bit userspace running under 64bit kernel o
On 2012-05-07 11:35, Michael Tokarev wrote:
> On 07.05.2012 18:18, Jan Kiszka wrote:
> []
>> I have a 32-bit WinXP here to test (but not a Win7-32) and will give it
>
> I just found out that a 32bit guest is not enough. The problem appears
> to be with 32bit userspace running under 64bit kernel o
On 07.05.2012 18:18, Jan Kiszka wrote:
[]
> I have a 32-bit WinXP here to test (but not a Win7-32) and will give it
I just found out that a 32bit guest is not enough. The problem appears
to be with 32bit userspace running under 64bit kernel only. I just
booted a 32bit kernel here on host, and no
On 2012-05-07 10:51, Michael Tokarev wrote:
> So, refreshing it all again with more correct information.
>
> First, it appears that only 32bit version of qemu userspace is
> affected, and only when using 32bit version of guest. So far,
> either 64bit qemu userpace or 64bit windows7 guest is enoug
So, refreshing it all again with more correct information.
First, it appears that only 32bit version of qemu userspace is
affected, and only when using 32bit version of guest. So far,
either 64bit qemu userpace or 64bit windows7 guest is enough
for the issue to not show up. Second, both win7 and
On 07.05.2012 14:16, Gleb Natapov wrote:
> On Mon, May 07, 2012 at 01:54:19PM +0400, Michael Tokarev wrote:
>> On 07.05.2012 12:06, Gleb Natapov wrote:
>>> On Mon, May 07, 2012 at 12:01:47PM +0400, Michael Tokarev wrote:
>> []
>> And the previously installed guest never reboots in currrent
On Mon, May 07, 2012 at 01:54:19PM +0400, Michael Tokarev wrote:
> On 07.05.2012 12:06, Gleb Natapov wrote:
> > On Mon, May 07, 2012 at 12:01:47PM +0400, Michael Tokarev wrote:
> []
> And the previously installed guest never reboots in currrent
> git version, always giving the 0x5c STOP c
On 07.05.2012 12:06, Gleb Natapov wrote:
> On Mon, May 07, 2012 at 12:01:47PM +0400, Michael Tokarev wrote:
[]
And the previously installed guest never reboots in currrent
git version, always giving the 0x5c STOP code after first
boot. This is aint good at all, as existing guests do
On 07.05.2012 12:06, Gleb Natapov wrote:
> On Mon, May 07, 2012 at 12:01:47PM +0400, Michael Tokarev wrote:
[]
>> I'm trying. But the problem is that right now I'm swamped
>> with other work. So far win7 x64 appears to work, it
>> reboots without showing this "stop" thing or other issues,
>> even
On Mon, May 07, 2012 at 12:01:47PM +0400, Michael Tokarev wrote:
> On 07.05.2012 11:45, Gleb Natapov wrote:
> > On Mon, May 07, 2012 at 10:06:58AM +0400, Michael Tokarev wrote:
> >> On 06.05.2012 23:03, Michael Tokarev wrote:
> >>> This is just a heads-up. I tried building current
> >>> qemu git t
On 07.05.2012 11:45, Gleb Natapov wrote:
> On Mon, May 07, 2012 at 10:06:58AM +0400, Michael Tokarev wrote:
>> On 06.05.2012 23:03, Michael Tokarev wrote:
>>> This is just a heads-up. I tried building current
>>> qemu git today and running a win7 guest in it. Neither
>>> already installed guest (
On Mon, May 07, 2012 at 10:06:58AM +0400, Michael Tokarev wrote:
> On 06.05.2012 23:03, Michael Tokarev wrote:
> > This is just a heads-up. I tried building current
> > qemu git today and running a win7 guest in it. Neither
> > already installed guest (which finds new hardware and
> > want to reb
On 06.05.2012 23:03, Michael Tokarev wrote:
> This is just a heads-up. I tried building current
> qemu git today and running a win7 guest in it. Neither
> already installed guest (which finds new hardware and
> want to reboot) nor freshly installed win7 boots:
> it boots for the first time, next
This is just a heads-up. I tried building current
qemu git today and running a win7 guest in it. Neither
already installed guest (which finds new hardware and
want to reboot) nor freshly installed win7 boots:
it boots for the first time, next it installs drivers,
but on reboot it BSODs with
STOP
19 matches
Mail list logo
