Arch Linux

nonsens

Member

Registered: 2010-08-19

Posts: 9

[solved]qemu-kvm, cant start all guests with latest qemu-kvm

Hi there!

I have a problem when I updated qemu-kvm package from 1.0.1-3 to 1.1.0-1

Some Linux guests can get started without problems but other will die after grub tries to load the kernel.

In my messages log i can find the following error when starting a affected guets:
qemu-kvm[2026]: segfault at 10 ip 00007f2845549d0e sp 00007f283d024c00 error 4 in qemu-system-x86_64[7f2845419000+308000]

After downgrading to the previous version i could start the guests again.

Did anyone had similar problems with the current qemu?

Kind regards

Edit: Upgrade to 1.1.1.1 solves the issue

Last edited by nonsens (2012-07-20 08:17:31)

Bluthund

Member

From: DE

Registered: 2012-07-08

Posts: 6

Re: [solved]qemu-kvm, cant start all guests with latest qemu-kvm

I encountered exactly the same problem with qemu-kvm 1.1.0-1 and a CentOS guest (2.6.32-220.23.1.el6.x86_64).

nonsens

Member

Registered: 2010-08-19

Posts: 9

Re: [solved]qemu-kvm, cant start all guests with latest qemu-kvm

Do you use disk image files or LVM Volumes?

I had that Problem as well with CentOS6 and Debian Weezy. Arch and Squeeze guests running smoothly

Bluthund

Member

From: DE

Registered: 2012-07-08

Posts: 6

Re: [solved]qemu-kvm, cant start all guests with latest qemu-kvm

My CentOS guest is running from a qcow2 image (via VirtIO).

guru42

Member

Registered: 2010-10-06

Posts: 4

Re: [solved]qemu-kvm, cant start all guests with latest qemu-kvm

Same Problem here!

/var/log/messages:

Jul 12 13:05:38 localhost kernel: [  420.218592] qemu-kvm: sending ioctl 5326 to a partition!
Jul 12 13:05:38 localhost kernel: [  420.218622] qemu-kvm: sending ioctl 80200204 to a partition!
Jul 12 13:05:46 localhost kernel: [  428.403101] qemu-kvm[2195]: segfault at 10 ip 00007f577a247d0e sp 00007f5772523c00 error 4 in qemu-system-x86_64[7f577a117000+308000]

All VM with LVM Volumes crash, the ones with image files seems too work.

fordboy0

Member

Registered: 2012-07-14

Posts: 1

Re: [solved]qemu-kvm, cant start all guests with latest qemu-kvm

qemu-kvm 1.1.0-1

Jul 14 11:12:43 localhost kernel: [  702.848853] device vnet0 entered promiscuous mode
Jul 14 11:12:43 localhost kernel: [  702.853007] br0: port 2(vnet0) entered forwarding state
Jul 14 11:12:43 localhost kernel: [  702.853011] br0: port 2(vnet0) entered forwarding state
Jul 14 11:13:04 localhost kernel: [  724.492513] qemu-kvm[3066]: segfault at 10 ip 00007f7eeea85d0e sp 00007f7ee635cc00 error 4 in qemu-system-x86_64[7f7eee955000+308000]

Guest is Arch, no LVM, VirtIO.  Switching to IDE, same issue.  Seems to die during udev triggering om the guest.

Downgrading to 1.0.1-3, problem disappears.

monzer4819

Member

Registered: 2009-03-26

Posts: 26

Re: [solved]qemu-kvm, cant start all guests with latest qemu-kvm

Sorry if I'm late to the party.    Had this problem too, saw a bug report but it was closed as an 'upstream' problem.     Anyways the problem appears to be a incompatibility with the libvirt VM config files.    I got my VM's working again by deleting the VM's (leaving the hard drives intact) and re-creating them.

All the VM's worked after that.   Only downside was that Win7 detected a hardware change and wanted to be reactivated.    Oh Windows.....

guru42

Member

Registered: 2010-10-06

Posts: 4

Re: [solved]qemu-kvm, cant start all guests with latest qemu-kvm

After some reading I found a workaround:

Edit the VM configuration with

#virsh edit <VM NAME>

and replace 'pc-0.15' with "pc-1.1'

 <os>
    <type arch='x86_64' machine='pc-1.1'>hvm</type>
    <boot dev='hd'/>
  </os>

The diff output of the changed /etc/libvirt/qemu/<VM_Name>.xml file with the saved one should look like:

#diff test.xml test.xml.sav
15c15
<     <type arch='x86_64' machine='pc-1.1'>hvm</type>
---
>     <type arch='x86_64' machine='pc-0.15'>hvm</type>

Now the changed VM start successful

Bluthund

Member

From: DE

Registered: 2012-07-08

Posts: 6

Re: [solved]qemu-kvm, cant start all guests with latest qemu-kvm

Yesterday's update to qemu-kvm 1.1.1 fixed it for me (without touching the VM configuration).