Qemu stopped working after update

vuokkosetae · 2015-10-09 11:29:00

I have ubuntu quest which I start with

$ qemu-system-x86_64 -enable-kvm -m 2G ubuntu-test -usbdevice tablet -soundhw hda -vga std

(process:6763): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported
WARNING: Image format was not specified for 'ubuntu-test' and probing guessed raw.
         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.

This worked quite nicely before system update. Now it opens small window with black screen, but doesn't boot any further. and one core is used 100%

kvm modules (kvm, kvm_intel) are loaded. dmesg or journalctl don't show anything related this problem.

All other quests seem to have this same problem.

Where should I look next?

ayekat · 2015-10-09 11:43:02

Is your disk image a raw image? It doesn't have an extension, so it's not very clear...

EDIT otherwise, have you tried booting something else? Perhaps a live system or something.

Last edited by ayekat (2015-10-09 11:43:46)

vuokkosetae · 2015-10-09 11:51:41

Yes. It is raw image. I tried to convert it to qcow2 but that didn't help either.

I tried

qemu-system-x86_64 -cdrom archlinux-2015.01.01-dual.iso -boot d

and it failed to mount /dev/disk/by-label/ARCH_201501 which would be the CD image!

And windows systems are unable boot too. I think there is something fishy in qemu and its way to handle image files.

Lone_Wolf · 2015-10-09 12:22:46

vuokkosetae, i don't think the image/glib warnings are the cause of your problems.

kvm modules (kvm, kvm_intel) are loaded

Your system has an intel processor CPU ?

If so, there have been some reports about trouble with qemu , intel processor and kernel 4.2.x .
What was the latest kernel version you had installed before the problems started ?

vuokkosetae · 2015-10-09 15:55:10

I have Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz
Well... I have in /var/cache/pacman/pkg/

linux-4.1.6-1-x86_64.pkg.tar.xz
linux-4.2.2-1-x86_64.pkg.tar.xz

So I'll try to downgrade to that one. It would be consistent with failing on reboot.

vuokkosetae · 2015-10-09 18:43:01

Downgrading kernel solved problem.

I don't like it, but it's best I have.

gigagoochelaar · 2015-10-09 21:07:59

Same GLib-Warning here, but my VMs still boot fine. The problem is today's upgrade to glib2-2.46.0-2. It will probably solve itself the next couple of days with a qemu upgrade.

brenix · 2015-10-10 07:40:36

Same issue here, my VM wont boot on 4.2.x and 4.3-rc4. Works fine on 4.1.x..

beanaroo · 2015-10-13 03:05:47

Same issue here.
Arch 4.2.2-1 ; qemu 2.4.0-4

Nektarios · 2015-10-13 22:54:05

Exact same issue here with Arch 4.2.3-1 and 2.4.0-4.

Disabling KVM on qemu with "no-kvm" option works fine (but very slow). Also works with using linux-lts (kernel downgrading). Therefore I guess there's a bug in KVM with 4.2.x kernels.

gigagoochelaar · 2015-10-15 08:59:20

The upgrade to qemu-2.4.0-4 didn't bring a solution indeed. The warning showed up the day I upgraded glib2, not after upgrading the kernel. Downgrading to glib2-2.44 removes the GLib-warning for me, even on linux-4.2.3

Nektarios · 2015-10-15 09:08:13

I found a workaround without kernel downgrade:

with kernel 2.4 and QEMU compat 2.3 works, so adding option:

-machine pc-i440fx-2.3

to qemu solves this and the VM starts up correctly.

cptG · 2015-10-21 10:12:57

I'm having the exactly same problem. Has anyone found / filed an upstream bug?

edit I figured better file a duplicate than none at all: https://bugs.launchpad.net/qemu/+bug/1508405

Last edited by cptG (2015-10-21 10:34:18)

ObamaBinFladen · 2015-10-23 14:56:53

I've got the same error
GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported

but i can't solve it with kernel downgrade (now I use the linux-vfio-lts kernel from AUR, which is currently at 4.1.10-1)
I need this kernel to fix my iommu group for an GPU passthrough, which I wanted to realize with QEMU 2.4.0.1.

I followed this this guide on Reddit to do the GPU Passthrough.

I tried -machine pc-i440fx-2.3 before. The Error disappears but now I don't get any video Signal on my passed-through GPU.

Here's my startscript if that helps anything

Any help appreciated!

belette · 2015-10-26 20:09:33

got the same issue when I launch qemu

(process:4101): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported

the VM is working this is definitiely after an upgrade of glib
anyone has any idea?

cptG · 2015-10-27 19:50:36

The Glib-Warning seems to not be a problem, I just ran git-bisect on the repo to find the commit that causes the failure and the versions that run, do so even with the warning.
If anyone is interested, the commit causing this problem is 355023f2010c4df619d88a0dd7012b4b9c74c12c - see the link to the bug-report in my post further up.

also: the error is - expect for the -enable-kvm and -machine parameters - independet of the VM configuration. A simple "qemu-system-x86_64 --enable-kvm" already shows the bug.

Last edited by cptG (2015-10-27 19:52:42)

cptG · 2015-10-28 09:24:50

Duh... I should've had a closer look at the commit I found. It clealry states that it introduces an SMM flag. So trying the following

qemu-system-x86_64 --enable-kvm -machine smm=off

solves the problem

...the commit message states that (if I don't misinterpret that) the parameter should be off for kvm by default so it seems that's where the bug is...

The property can take values on, off or auto. The default is "off"
for KVM and pre-2.4 machines, otherwise "auto" (which makes it
available on TCG or on new-enough kernels).

Last edited by cptG (2015-10-28 09:28:45)

ObamaBinFladen · 2015-11-02 03:37:25

cptG wrote:

Duh... I should've had a closer look at the commit I found. It clealry states that it introduces an SMM flag. So trying the following
qemu-system-x86_64 --enable-kvm -machine smm=off
solves the problem
...the commit message states that (if I don't misinterpret that) the parameter should be off for kvm by default so it seems that's where the bug is...
The property can take values on, off or auto. The default is "off"
for KVM and pre-2.4 machines, otherwise "auto" (which makes it
available on TCG or on new-enough kernels).

That one did it for me, thank you!

brenix · 2015-11-03 03:22:17

Trying to add this option in my libvirt xml, but get validation errors etc.. Anyone know where/how to add this for a libvirt guest?

sheyll · 2015-11-16 18:29:59

@brenix

I have the same problem, I also did not manage to pass the

-machine smm=off

option.

This is my failed attempt:

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <os>
    <type>hvm</type>
    <boot dev='hd' />
  </os>
  <qemu:commandline>
    <qemu:arg value='-machine smm=off'/>
  </qemu:commandline>

I got this error:

error: internal error: process exited while connecting to monitor: qemu-system-x86_64: -machine smm=off: invalid option

Then I remembered Nektarios idea about using a specific machine type and now I am experimenting with this:

  <os>
    <type machine='pc-i440fx-2.3'>hvm</type>
    <boot dev='hd' />
  </os>

I haven't done any performance measurements, but this works for now.

Good luck,
Sven

Last edited by sheyll (2015-11-16 18:34:58)

Arch Linux

#1 2015-10-09 11:29:00

Qemu stopped working after update

#2 2015-10-09 11:43:02

Re: Qemu stopped working after update

#3 2015-10-09 11:51:41

Re: Qemu stopped working after update

#4 2015-10-09 12:22:46

Re: Qemu stopped working after update

#5 2015-10-09 15:55:10

Re: Qemu stopped working after update

#6 2015-10-09 18:43:01

Re: Qemu stopped working after update

#7 2015-10-09 21:07:59

Re: Qemu stopped working after update

#8 2015-10-10 07:40:36

Re: Qemu stopped working after update

#9 2015-10-13 03:05:47

Re: Qemu stopped working after update

#10 2015-10-13 22:54:05

Re: Qemu stopped working after update

#11 2015-10-15 08:59:20

Re: Qemu stopped working after update

#12 2015-10-15 09:08:13

Re: Qemu stopped working after update

#13 2015-10-21 10:12:57

Re: Qemu stopped working after update

#14 2015-10-23 14:56:53

Re: Qemu stopped working after update

#15 2015-10-26 20:09:33

Re: Qemu stopped working after update

#16 2015-10-27 19:50:36

Re: Qemu stopped working after update

#17 2015-10-28 09:24:50

Re: Qemu stopped working after update

#18 2015-11-02 03:37:25

Re: Qemu stopped working after update

#19 2015-11-03 03:22:17

Re: Qemu stopped working after update

#20 2015-11-16 18:29:59

Re: Qemu stopped working after update

Board footer