LinuxQuestions.org - [SOLVED] KVM: Error starting domain: internal error: process exited while connecting to monitor:

- Linux - Virtualization and Cloud (https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/)

- - KVM: Error starting domain: internal error: process exited while connecting to monitor: (https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/kvm-error-starting-domain-internal-error-process-exited-while-connecting-to-monitor-4175605414/)

KVM: Error starting domain: internal error: process exited while connecting to monitor:

Hello,

I found this post that has the same problem as me but I am not able to figure this out. I am using Slackware 14.2 and KVM/Qemu.
https://bbs.archlinux.org/viewtopic.php?id=190762

This was caused, I believe, because I updated the packages in my system. I don't know to what XML the above link it is referring to and how to locate and restore the symlink if I have to. I apologize for any lack of information but I shall be quick to provide it. Below are the details I get from Virtual Machine Manager. Thanks for any help.

Details:
Error starting domain: internal error: process exited while connecting to monitor: 2017-05-07T03:38:36.470418Z qemu-kvm: -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 88, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 124, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1404, in startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1035, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor: 2017-05-07T03:38:36.470418Z qemu-kvm: -msg timestamp=on: Unsupported machine type
Use -machine help to list supported machines!

post the contents of the following command:

Code:

cat /etc/libvirt/qemu/*.xml | grep \<name'\|machine'

Thanks Slax-Dude:

Code:

# cat /etc/libvirt/qemu/*.xml | grep \<name'\|machine'

  <name>win7</name>

    <type arch='x86_64' machine='pc-i440fx-2.6'>hvm</type>

what about

Code:

qemu-system-x86_64 -machine ?

Here is the output:

Code:

# qemu-system-x86_64 -machine ?

Supported machines are:

pc                  Standard PC (i440FX + PIIX, 1996) (alias of pc-i440fx-2.4)

pc-i440fx-2.4        Standard PC (i440FX + PIIX, 1996) (default)

pc-i440fx-2.3        Standard PC (i440FX + PIIX, 1996)

pc-i440fx-2.2        Standard PC (i440FX + PIIX, 1996)

pc-i440fx-2.1        Standard PC (i440FX + PIIX, 1996)

pc-i440fx-2.0        Standard PC (i440FX + PIIX, 1996)

pc-i440fx-1.7        Standard PC (i440FX + PIIX, 1996)

pc-i440fx-1.6        Standard PC (i440FX + PIIX, 1996)

pc-i440fx-1.5        Standard PC (i440FX + PIIX, 1996)

pc-i440fx-1.4        Standard PC (i440FX + PIIX, 1996)

pc-1.3              Standard PC (i440FX + PIIX, 1996)

pc-1.2              Standard PC (i440FX + PIIX, 1996)

pc-1.1              Standard PC (i440FX + PIIX, 1996)

pc-1.0              Standard PC (i440FX + PIIX, 1996)

pc-0.15              Standard PC (i440FX + PIIX, 1996)

pc-0.14              Standard PC (i440FX + PIIX, 1996)

pc-0.13              Standard PC (i440FX + PIIX, 1996)

pc-0.12              Standard PC (i440FX + PIIX, 1996)

pc-0.11              Standard PC (i440FX + PIIX, 1996)

pc-0.10              Standard PC (i440FX + PIIX, 1996)

q35                  Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-2.4)

pc-q35-2.4          Standard PC (Q35 + ICH9, 2009)

pc-q35-2.3          Standard PC (Q35 + ICH9, 2009)

pc-q35-2.2          Standard PC (Q35 + ICH9, 2009)

pc-q35-2.1          Standard PC (Q35 + ICH9, 2009)

pc-q35-2.0          Standard PC (Q35 + ICH9, 2009)

pc-q35-1.7          Standard PC (Q35 + ICH9, 2009)

pc-q35-1.6          Standard PC (Q35 + ICH9, 2009)

pc-q35-1.5          Standard PC (Q35 + ICH9, 2009)

pc-q35-1.4          Standard PC (Q35 + ICH9, 2009)

isapc                ISA-only PC

none                empty machine

Do you see your problem yet? :)

I have looked up more information to see it. The current XML has

Code:

type arch='x86_64' machine='pc-i440fx-2.6

but it seems that it is no longer supported from the output in

Code:

# qemu-system-x86_64 -machine ?

Do I just change the XML line "2.6" to "2.4"? This is not clear to me, yet. Thanks Slax-Dude for your didactic approach.

Now that you can fish, I can buy you lunch :)

It is best to describe machine type as 'pc' as it will always point to the latest version supported of the pc-i440fx chip-set.
Better choice would be 'q35' as it is a more recent chip-set.

I almost had a free lunch :cry:. I am not sure what I am doing wrong:

Code:

# virsh edit win7

error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng

Extra element devices in interleave

Element domain failed to validate content



Failed. Try again? [y,n,i,f,?]:

I am replacing this line in the XML

Code:

type arch='x86_64' machine='pc-i440fx-2.6'

with this one

Code:

type arch='x86_64' machine='q35'

and also tried this line

Code:

type arch='x86_64' machine='pc-q35'

but I get the error above. Any ideas? :scratch:

Try 'pc' for a safe choice.
Note that the "machine" parameter defines the chip-set, and not all chip-sets are compatible with all virtual hardware.
This may happen when you define a VM with one version of virt-manager then use it with another version, although more often problems happen from new to old versions not the other way around.

Also, you could try stopping the libvirt service and edit the .xml file with your favorite text editor.

I actually tried 'pc' too and same thing. I stopped the libvirt service:

Code:

/etc/rc.d/rc.libvirt stop

And then edited the XML file with vi but changes were re-written as warned when not done through virsh edit. Also, virsh edit does not work when the libvirt services have been stopped. Thanks for any continued help.

I made some updates as mentioned and this affected the generic kernel thus not being able to run the guest OS. I am able to run it with the Huge kernel. I shall try to fix the generic kernel issue now. Thanks Slax-Dude for helping me get this far.