https://bugzilla.novell.com/show_bug.cgi?id=704537 https://bugzilla.novell.com/show_bug.cgi?id=704537#c0 Summary: qemu-kvm crashes the first time a guest VM is started after booting Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: gvenkat@attglobal.net QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=438879) --> (http://bugzilla.novell.com/attachment.cgi?id=438879) Log User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 I use virsh to start Windows guest and use SPICE client to access the desktop. If I start the Windows VM domain the first time after a reboot and connect to it via SPICE, it crashes within a minute or two without doing anything. A restart of the domain in virsh works without any problems. Logs and version info given below. This problem started to appear since one of the builds of kvm in the last few months Reproducible: Always Steps to Reproduce: 1. Reboot host 2. Start Windows XP (or 7) VM domain from virsh 3. Connect from remote SPICE client 4. Wait for the crash/shutdown of guest VM Actual Results: The guest VM is shutdown. There are no errors in the guest VM logs. It is like a forced power off as far as the guest is concerned. Expected Results: KVM should not crash the guest VM KVM compiled from source at http://download.opensuse.org/repositories/Virtualization/openSUSE_11.4/src/ using just --with spice parameter to rpmbuild Current software versions: Kernel 2.6.37.6-0.5-desktop KVM kvm-0.14.1.0-108.1.x86_64 libvirt libvirt-0.9.3-138.2.x86_64 spice-client spice-client-0.8.1-1.1.x86_64 soice server libspice-server1-0.8.1-1.1.x86_64 Note the very large memory allocation to the qxl graphics driver in the qemu-kvm command line in the attachment. Don't know if this is relevant. Please do keep in mind that this always happens ONLY on the first start of a VM, not subsequent starts so the bug can only be in things that persist over multiple invocations which rules out many of the components. The only log entry tied to this event is the virtio trying to map MMIO memory which doesn't appear on subsequent starts where it doesn't crash. This is the most obvious clue. Perhaps there is a timeout error when this is attempted the first time but is done and available for subsequent starts which may indicate a problem with upstream qemu in the kernel. I am just guessing here. Don't have any experience with the code or architecture of these components. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.