On Mon, Jul 19, 2010 at 10:17:02AM +0300, Harri Olin wrote: > Gleb Natapov kirjoitti: > >On Thu, Jul 15, 2010 at 03:19:44PM +0200, Christoph Adomeit wrote: > >> > >>But one Windows 2008 64 Bit Server Standard is freezing regularly. > >>This happens sometimes 3 times a day, sometimes it takes 2 days > >>until freeze. The Windows Machine is a clean fresh install. > >> > >>By Freezing I mean that the Machine console still shows the > >>windows logo but does not accept any keystroke and does not > >>answer > >>to ping or rdp or whatever. The virtual cpu-load is then shown > >>as 100% (by proxmox). > > Hi > > I think I have seen same problem occur on my Windows 2008 SBS SP2 > 64bit system, but a bit less often, only like once a week. > > Short description of system: > Supermicro X7SBL-LN2 motherboard, Q8300 cpu, 8GB memory, Areca > ARC-1210 RAID controller. > > Linux kernel 2.6.33.1, qemu-kvm-0.11.1, windows 2008 quest is the > only one at the moment. > > I had to step down to 0.11.1 from 0.12.x as that was more unstable, > windows 2008 bluescreened every second day. Also 0.11.1 did the same > when I applied -rtc-td-hack, I think. (might also be -cpu host, > which I removed at the same time but I think the crashing started > when I added -rt-td-hack). > Sample bluescreen error codes from that time: > 0x0000003b (0x00000000c0000005, 0xfffff80001cb8842, 0xfffffa600 > 0x0000003b (0x00000000c0000005, 0xfffff80001c9c842, 0xfffffa600 > 0x0000000a (0x0000000000000080, 0x000000000000000c, 0x000000000 > 0x0000003b (0x00000000c0000005, 0xfffff80001c5d842, 0xfffffa600 > Also I think I have seen qemu crashing once.. > > Now I haven't seen crashes but only freezes with qemu on 100% and > virtual system unresponsive. > > qemu command line: > /usr/local/qemu-kvm-0.11.1/bin/qemu-system-x86_64 -drive > file=/dev/rigelvg/w2k8system,cache=none,boot=on -drive > file=/dev/rigelvg/w2k8data,cache=none -m 6144 -vnc :1 -net > nic,macaddr=C0:FF:12:FB:AA:01,model=e1000 -net tap -smp 4 -localtime > > Try with different model then e1000 please. Default driver that comes with Windows known to have problems. > >When hang occurs ensure that problematic vm is the only on on the server and run > >kvm_stat. Send output here. Also do the following: > > > ># mount -t debugfs debugfs /sys/kernel/debug > ># echo kvm > /sys/kernel/debug/tracing/set_event > ># sleep 1 > ># cat /sys/kernel/debug/tracing/trace > /tmp/trace > > > >Send /tmp/trace here too, but it may be huge, so send only last 1000 > >lines. > -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html