[libvirt-users] Internal error reported by libvirt while creating a VM

[Andrea Bolognani]

On Mon, 2019-09-30 at 15:43 -0400, Ajay Kumar wrote:
> Hi, am Ajay Kumar.

Please don't CC random libvirt developers when posting to the mailing
lists.

> I am trying to create a virtual machine on the remote host (where libvirt 5.8.0) was installed using a virtual machine manager which are running on the local ubuntu machine.
> 
> The specification of my remote host are:
> Hypervisor: KVM
> QEMU version: QEMU emulator version 2.4.0.1, Copyright (c) 2003-2008 Fabrice Bellard
> The below error is propagating when I am trying to install KVM-VMI (https://github.com/KVM-VMI/kvm-vmi/tree/kvmi) with modified QEMU, and there is a modified QEMU involved, in  /usr/local/bin/qemu-system-x86_64. 
> 
> The below particular error propagating when I am trying to create a virtual machine using VMM gui (virt-manager).
> 
> 
> Unable to complete install: 'internal error: process exited while connecting to monitor: 
> (process:7400): GLib-WARNING **: 18:19:45.044: ../../../../glib/gmem.c:489: custom memory allocation vtable not supported
> 2019-09-30T18:19:45.046714Z qemu-system-x86_64: -msg timestamp=on: Unsupported machine type
> Use -machine help to list supported machines!'
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
>     callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/create.py", line 2553, in _do_async_install
>     guest.start_install(meter=meter)
>   File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install
>     doboot, transient)
>   File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest
>     domain = self.conn.createXML(install_xml or final_xml, 0)
>   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3603, in createXML
>     if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
> libvirtError: internal error: process exited while connecting to monitor: 
> (process:7400): GLib-WARNING **: 18:19:45.044: ../../../../glib/gmem.c:489: custom memory allocation vtable not supported
> 2019-09-30T18:19:45.046714Z qemu-system-x86_64: -msg timestamp=on: Unsupported machine type
> Use -machine help to list supported machines!

My guess would be that your modified QEMU does not support whatever
machine type the guest is configured to use.

What's in the

  <type arch='x86_64' machine='xxx'>hvm</type>

element, and is that machine type listed in the output of

  qemu-system-x86_64 -machine help

?

-- 
Andrea Bolognani / Red Hat / Virtualization