Toni Mueller wrote: > Hi Michael, > > On Fri, 12.03.2010 at 21:58:44 +0300, Michael Tokarev <m...@tls.msk.ru> wrote: >> From what you provided above it sounds like some sort of i/o >> problem, but without much more details (exact kvm command line, >> kinds of disk devices you use, and some sorts of traces it is >> impossible to say what's going on. > > although my interest in KVM is waning quickly, as I really need support > for other platforms as well, I've produced two dmesg files for my Lenny > and Sid machines. I've done both with the old qemu-kvm package, though, > and have to note that the Sid kvm does not start with the > 2.6.32-3 kernel (but hangs at the tsc clocksource unstable message that > you declared benign). > > The command lines are: > > --------------- cut > kvm -localtime -no-acpi -m 512 \ > -net nic,model=rtl8139,macaddr=52:54:00:12:34:56,vlan=0 \ > -daemonize \ > -net tap,vlan=0 /mounts/vmachines/kvm/d-sid/sid1.img & > --------------- cut
Ugh, can you retry without -no-acpi? -no-acpi is basically asking for one or another trouble... But in any way, the dmesg traces you provide look quite good, and there's nothing in the kernel/dmesg which indicates to any problem... What I mean above referring to "i/o error" is some internal stuff. When I/O in kvm fails, it usually happens silently, but guest _may_ indicate something in dmesg like "i/o error reading block 1234 on dev sda". In your case nothing like that happened. Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
