libvirt users - Sep 2019 - Internal error reported by libvirt while creating a VM

Hi, am Ajay Kumar.

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!





-- 
*With Best Regards:*
Ajay

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

On Tue, 2019-10-01 at 17:55 -0400, Ajay Kumar wrote:
> Hi Andrea,
> 
> Thank you for your response. Sure I don't CC  to libvirt developers.
Please keep the list in the loop, though! I've re-added it.
> I am getting an error while creating a Win10 virtual machine using VMM or
virt-manager GUI.
> I could configure the windows 10 quest using its XML file only ofter
creating a VM using virt-manager GUI in the following the path
/etc/libvirt/qemu.
> 
> The modified QEMU emulator is running correctly 
> @ubuntu-kvm3:/usr/local/bin$ ls
> ivshmem-client  qemu-ga   qemu-io   qemu-pr-helper      virsh      
virt-host-validate  virt-pki-validate  vmi-dump-memory  vmi-process-list 
vmi-win-offsets
> ivshmem-server  qemu-img  qemu-nbd  qemu-system-x86_64  virt-admin 
virt-login-shell    virt-xml-validate  vmi-module-list  vmi-win-guid
This only proves that you've installed it, not that it works.

And as I said, the modified binary probably works fine on its own but
libvirt might not be able to drive it, at least without tweaks.
> @ubuntu-kvm3:/etc/libvirt/qemu$ ls
> networks
Just for the record, you're not supposed to modify files in
/etc/libvirt/qemu directly; use virsh instead.
> I couldn't see guest XML file here(because the VM creation was not
done).
> attached snap displaying error while creating a VM. 
If you run

  $ virt-manager --debug

from the command line you will get a lot of output, including the
XML that's passed to libvirt. Please attempt the installation again,
capture that output in a plain text file and send it to the list as
an attachment.

Also run

  $ /usr/local/bin/qemu-system-x86_64 -machine help

and attach the output of that command, too.

That should help us figure out what's wrong.

-- 
Andrea Bolognani / Red Hat / Virtualization

Re-added the list. Please *do not* drop the libvirt-users mailing
list from the recipients again!

On Thu, 2019-10-03 at 16:42 -0400, Ajay Kumar wrote:
> Hi Andrea, 
> 
> Thank you for your help,
> 
> The above issues are addressed while reinstalling libvirt 4.0.0. Currently,
I could create a VMs on libvirt.
> 
> I have another issue while configuring/editing win10.xml file.
> After edit or insert of few lines in win10.XML file using virsh i.e at     
/etc/libvirt/qem$ virsh edit win10
Saying that you changed "few lines" is not at all useful: if you
hope to get any help from the list, you'll have to share the *exact*
changes you made each time and the full XML configuration that
resulted from them.
> I am getting a below error. 
> @ubuntu-kvm3:/etc/libvirt/qemu$ virsh edit win10
> error: internal error: Child process (LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
/usr/local/bin/qemu-system-x86_64 -help) unexpected exit status 126: libvirt: 
error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission
denied
> 
> I understand that this could be the problem of AppArmor security feature it
doesn't allow new binary such as (qemu-system-x86_64) to execute
> 
> Later I have followed the below link to address 
> [ 
https://www.reddit.com/r/VFIO/comments/9pi2cd/how_to_set_up_qemu_30_on_ubuntu_1804/
> 6. Create AppArmor rules so libvirt can use the binary  ]
> 
> here i have added few lines in 2 files as per the procedure. later when i
restart apparmor I got the below error
Again, saying that you added "few lines" is not helpful because we
have no idea what those lines look like, so it's simply impossible
for anyone to figure out the root cause of the error message you're
seeing. Please share the *exact* changes you made.

-- 
Andrea Bolognani / Red Hat / Virtualization