similar to: [Solved]：LibvirtError: Operation not supported : JSON monitor is required

Hi Thanks for chenhanxiao@cn.fujitsu.com help , I have resole the problem (libvirt 1.2.4 and virt-manager 0.9.0 are not incompatible)..but when I created VM by virt-manager ,it reported : unable to complete install: 'Opertation not supported: JSON monitor is required.' Traceback(most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py",line

Hello everyone I encountered a problem when I completed the update of libvirt from 0.10 to 1.2.4 . The problem was that virt-manager(version 0.9.0) could not start and reported error : "ImportError: /usr/lib64/libvirt.so.0: version 'LIBVIRT_PRIVIATE_0.10.2' not found (required by /usr/lib64/python2.6/site-packages/libvirtmod.so)". I found the libvirt.so.0 link

Hi I have reinstall Fedora 20 from distrib. I have run yum update and yum upgrade. Running kernel is : 3.14.7-200.fc20.x86_64 Installed Libvirt packages are: libvirt-client-1.1.3.5-2.fc20.x86_64 libvirt-daemon-1.1.3.5-2.fc20.x86_64 libvirt-daemon-config-network-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-interface-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-network-1.1.3.5-2.fc20.x86_64

These are the messages that I get when trying to attach a virtio disk to or perform a shutdown of the problem vm guest. Add hardware This device could not be attached to the running machine. Would you like to make the device available after the next guest shutdown? Requested operation is not valid: cannot do live update a device on inactive domain Traceback (most recent call last): File

On Sun, Jun 15, 2014 at 09:01:29AM +0300, Patrick Chemla wrote: [. . .] > When trying to create a new VM using virt-manager I am getting : > > Impossible de terminer l'installation : « internal error: process exited > while connecting to monitor: Failed to create chardev > » > > Traceback (most recent call last): > File

Hi. I am very interested in the security properties a totally open TPM can give our users? - its use as a universal smartcard to protect all types of keys. When adding the virtual 1.2 or 2.0 TPM I get the vague error below. OS is Debian stable with standard packages. Error starting domain: Unable to find 'swtpm' binary in $PATH: No such file or directory Traceback (most recent call

hello, i rsynced a kvm vm from one host to another. i start virt-manager and tell virt-manager to use an existing disk. i set cpu to haswell that is on the host. configure before start is set, and i start "begin installation". I get this output by virt-manager: Unable to complete install: 'internal error: process exited while connecting to monitor: 2017-07-19T09:27:10.861928Z

hello mailinglist, on gentoo system with qemu-1.6.1, libvirt 1.1.4, libvirt-glib-0.1.7, virt-manager 0.10.0-r1 when i set on virtual machine "cache=none" in the disk-menu, the machine faults to start with: << Fehler beim Starten der Domain: Interner Fehler: Prozess während der Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: -drive

On all of the networks I create, I really don't want libvirt/KVM/virt-manager to do any kind of DHCP. I'm currently using xml files to feed into libvirt via virsh, for example: <network> <name>192_0_1</name> <bridge name='swan01' stp='on' delay='0' /> <mac address='12:00:00:16:16:BA'/> <ip

Hi Guys, I am trying to add a Broadcom Physical NIC to a virtual Machine as Passthrough device. However I am getting following error. Error starting domain: unsupported configuration: host doesn't support passthrough of host PCI devices Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper

I have a PCI sound card that I would like to assign to a VM, but when I try to do so the VM fails to start and displays this message: Error starting domain: Unable to read from monitor: Connection reset by peer Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper callback(asyncjob, *args, **kwargs) File

On Wed, Jul 19, 2017 at 11:45:36AM +0200, Marko Weber | 8000 wrote: > > hello, > i rsynced a kvm vm from one host to another. > i start virt-manager and tell virt-manager to use an existing disk. > i set cpu to haswell that is on the host. > > configure before start is set, and i start "begin installation". > I get this output by virt-manager: > > Unable

hello list, i cant create an isolated network with the virt-manager. installed version virt-manager 3.0.0 installed version libvirt 6.2.0 output in error-message: Error creating virtual network: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr3 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No

hello list, creatig a virtual network via virt-manager fails. gentoo linux vanilla-sources 5.3.1 virt-manager 2.2.1 qemu 4.0 libvirt 5.5.0 the error output of Error creating virtual network: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr1 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No

I have set root in both for user and group in the qemu.conf and changed the file permissions to root like it was before. Now I'm getting this error: *# Error 1#* *Unable to complete install: 'internal error: process exited while connecting to monitor: us=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device

Hi, After full new install of Fedora 19 or 20, I am getting this when I want to create a new VMs. Impossible de terminer l'installation : « Unable to create vcpu cgroup for fedora20(vcpu: 0): Aucun fichier ou dossier de ce type » Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args,

I have installed OVS from sources using the installation steps mentioned on this link: http://docs.openvswitch.org/en/latest/intro/install/general/ I had installed libvrt, KVM, QEMU and all the necessary packages using apt-get. My KVM-QEMU hypervisor has been running well. To add a VM with the port attached to OVS bridge I changed the XML domain file as per the instructions on this page:

On 03/14/2013 03:17 AM, Digvijay wrote: > [root at node0 ~]# virsh migrate --live try1 qemu+ssh://root at 100.100.102.106/system > --unsafe > root at 100.100.102.106's password: > error: operation failed: migration job: unexpectedly failed > error: Reconnected to the hypervisor > CC-ing libvirt-users I think that virsh command should work. Look at

I just upgrade to the last version of the libvirt on my Gentoo System. (From 0.9.6 to 0.9.10-r3) But i have a problem with starting my NAT: Error starting network 'NAT': Cannot open network interface control socket: Address family not supported by protocol Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper

Hello, I've installed Xen 4.3.1 on a machine with x86 based 64-bit Intel processor running Fedora 20 (Linux 3.11) and libvirt 1.0.1. I'm not able to start a VM. It's failing with the below mentioned error. What am I doing wrong? If this is documented somewhere, a pointer to that would be great. I did a "generic" search, but in vain, before posting to this list and I