Toni Mueller wrote: > Hi Michael, Hello!
> On Fri, 12.03.2010 at 21:58:44 +0300, Michael Tokarev <m...@tls.msk.ru> wrote: >> Toni, please verify if this bug is present in the current >> version of qemu-kvm in unstable (0.12.3+dfsg-4). If you >> don't like using unstable, try out qemu-kvm from my page >> (http://www.corpit.ru/debian/tls/kvm/ - grab the qemu-kvm.deb >> for your arch) > > I've installed this package, just fetched from your site: > > qemu-kvm_0.12.3-tls0_amd64.deb > > With this command line: > > # kvm -localtime -m 512 -net nic,model=e1000,macaddr=52:54:00:12:34:56,vlan=0 > -net tap,vlan=0 /mounts/vmachines/kvm/d-sid/sid2.img > > and this kernel package: > > linux-image-2.6-686, implying linux-image-2.6.32-3-686 (2.6.32-9), I > was able to reproduce the problem. I was also able to reproduce the > problem with the other VM, sid1.img, so I think it's unlikely to hit > two otherwise undetected physical disk surface problems at the same > time. Toni, yet again, please, pretty please, read what I wrote. I refer to _virtual_ disk error, not to _physical_ disk error. Some bug in kvm (for example) causing _virtual_ disk to fail, -- and here, guest behaves one or another way, including all freezing I/O. > The system log shows this: > > kvm: 7842: cpu0 unhandled rdmsr: 0x417 > > But otherwise, there are no error messages present. Ok, that's good. Something to work with. Toni, can you please boot your guest with clocksource=acpi_pm kernel boot option? Also, try loading kvm module on host with ignore_msrs=1 before running guests. Have you seen this "cpu0 unhandled rdmsr: 0x417" messages when your other guests were hanging? 0x417 is machine check exception register. The question is why the guest is asking for it (there is a code which does periodic pooling), and why kvm is failing to handle it, which should not happen. But again, please don't spend much time on this UNLESS it is the message which accomplishes other guests stalls. > I then proceeded to install a backport of libasound2 to gain the > ability to use these packages: > > kvm_0.12.3+dfsg-5tls_amd64.deb and > qemu-kvm_0.12.3+dfsg-5tls_amd64.deb > > and then I tried again, but nothing changed (and no logs, too). These should be the same as 0.12.3-tls0 you tried above, at least when our problem is concerned. Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
