Sory for so useless bug report, but it is very hard to reproduce this.
Problems shows up only then 2 or more VM's are running on host (doe's
not noticed such crashes then only one VM is on). And blue screen shows
at unpredictable time for very short time and system reboots - no way to
see more information whats on (or w2k3 dumps and logs must be analyzed
after crash - but I am not big Windows guru). VM is started using
libvirt - using libvirt formatted kvm command line, but after crash
nothing interesting in  kvm log file.
On some host squeeze and wxp guests are running - but for them there are
no problems.

It's really needs some more work to find that's on, but is this needed
if in git this is already somehow fixed?

So this bug report is more like wish - please upgrade to new one and may
be even not stable upstream release, because it looks like latest stable
is not stable at all.
 
If you need some more info to reproduce bug - please point what is
needed most.

Best regards

Tomas Martišius


On 05/08/2012 08:59 PM, Michael Tokarev wrote:
> tags 672112 + moreinfo unreproducible pending
> thanks
>
> On 08.05.2012 17:23, Tomas Martišius wrote:
>> Package: qemu-kvm
>> Version: 1.0+dfsg-11
>>
>> Severity: serious
>>
>> qemu-kvm VM W2K3 quest reboots (crashes with blue screen) when there are 
>> several VM on intel xeon server and some server load/IO wait.
> I haven't ran w2k3 guests for a while.  Now I tried running my old guest,
> but I can't reproduce the problem.  So please provide steps to reproduce.
>
>> After qemu-kvm package rebuilt using latest (2012-04-27) source from git 
>> problem does not shows any more.
> That's good to know.  So I'll mark this bugreport as "done" automatically
> once we upload next release of qemu-kvm.  Tagging as "pending".  So thank
> you for the best bugreport out there -- completely useless since it has no
> details whatsoever and is already fixed... ;)
>
> /mjt




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to