15.08.2011 17:39, Miguel Mismo wrote: > >> Can you try booting without virt-manager, with just one >> vCPU please? >> So that we can narrow it down to particular combination. > > Ok, I tried with the following command following your instructions (1 CPU). > It's a modification from what gives libvirt: > > /usr/bin/kvm -M pc-0.12 -enable-kvm -m 614 -smp \ > 1,sockets=1,cores=1,threads=1 -name ... -uuid ... \ > -nodefaults -rtc base=utc -boot c \ > -drive file=...,if=none,id=drive-ide0-0-0,boot=on,format=raw \ > -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 \ > -device e1000,vlan=0,id=net0,mac=...,bus=pci.0,addr=0x3 -usb \ > -device usb-tablet,id=input0 -k es -vga cirrus \ > -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 > > > I launched it 10 times, and yes, it booted without problems.
Ok, that gives us something as a starting point. Now to find out what breaks when you start it from libvirt. Several vCPUs? >> 2.6.32-35 to be exact. > > I'll give exact kernel versions: > > On squeeze vm's: > > $ uname -r > 2.6.32-5-amd64 That will be seen on output of uname -r on all squeeze kernels, since they're all of this "version". What matters here alot is the debian package revision number, or complete debian version of the kernel package. dpkg -l | grep linux-image will give this info, and it will look like that 2.6.32-35 I quoted (I found it in your original bugreport in autogenerated section). Thank you, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
