On Wed, May 08, 2013 at 02:51:48PM +0200, Tomas Papan wrote: > Hi, > > No nothing, I check all logs (even syslog) > Yeah, since status of the vm is "running" you are not suppose to see there anything.
> 1) virsh # qemu-monitor-command vm-jack --hmp info status > VM status: running > > 2) morpheus@anakin ~ $ ps aux | grep vm-jack > qemu 3822 0.5 0.1 8952256 23600 ? Sl 13:59 0:08 > /usr/bin/qemu-system-x86_64 -machine accel=kvm -name vm-jack -S > -machine pc-0.14,accel=kvm,usb=off -cpu > Nehalem,+rdtscp,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme > -m 8192 -smp 4,sockets=4,cores=1,threads=1 -uuid > 03196c23-24ba-d398-a000-582b0e88b0e7 -no-user-config -nodefaults > -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm-jack.monitor,server,nowait > -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc > -no-shutdown -boot order=c,menu=on -device > piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive > file=/var/lib/libvirt/images/jack.img,if=none,id=drive-virtio-disk0,format=raw > -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 > -drive > file=/var/lib/libvirt/images/kernel.img,if=none,id=drive-virtio-disk1,format=raw > -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 > -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device > ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev > tap,fd=19,id=hostnet0 -device > e1000,netdev=hostnet0,id=net0,mac=52:54:00:21:1c:e0,bus=pci.0,addr=0x3 > -chardev pty,id=charserial0 -device > isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -k en-us > -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 > > 3) it took some time, I didn't have debug_fs, then tracing... but the > file is stored here (15 MB) http://papan.sk/share/trace.dat.tar.gz > Very interesting. In the middle of the run vcpu decides that it does not want to run any more. How much cpu time qemu takes when it happens? If it is 100% can you do the following: 1. run qemu-monitor-command vm-jack --hmp info cpus 2. note thread id for cpu #0 3. run "trace-cmd record -P $pid -p function" where $pid is the pid thread id that you've found in 2. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
