[SOLVED] KVM: Error starting domain: internal error: process exited while connecting to monitor:
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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!
# 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
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 . 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,?]:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.