similar to: Guests automatically stuck on pause

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

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

Hello, I keep receiving errors such as the following: Error rebooting domain: Timed out during operation: cannot acquire state change lock (held by qemuProcessReconnect) Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in cb_wrapper callback(asyncjob, *args, **kwargs) File

On 8/19/19 9:53 PM, Nir Soffer wrote: > Hi, > > I upgraded to a Fedora 29 host using virt-preview repo to > libvirt-daemon-5.6.0-1.fc29.x86_64 > The host was using plain Fedora 29 without virt-preview before that. > > After the upgrade, starting some vms that were running fine fail now with > this error: > > Error starting domain: internal error: child reported

On Sat, Oct 05, 2019 at 02:32:19PM +0000, procmem@riseup.net wrote: >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

Hi everyone and Martin I would like to confirm the conversation we had in regard the possible limitation of firmware auto-select feature that’s been released since v5.20. I recall you saying that there were a lot of issues with auto select and later they shipped it into a Json file , it still didn’t solve all the problems, did it? Is it better to explicitly specify the loader and nvram path

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:

I added libvirt-users@redhat.com back to the Cc for this response. Please don't remove the list address when responding to postings on a mailing list. A message to the list is *much* more likely to reach someone who knows the answer than is a private message to a single person. On 3/26/19 10:03 AM, Harsh Gondaliya wrote: > Mar 26 19:25:01 dpdk-OptiPlex-5040 libvirtd.service: 20423:

Hi, I upgraded to a Fedora 29 host using virt-preview repo to libvirt-daemon-5.6.0-1.fc29.x86_64 The host was using plain Fedora 29 without virt-preview before that. After the upgrade, starting some vms that were running fine fail now with this error: Error starting domain: internal error: child reported (status=125): Requested operation is not valid: Setting different DAC user or group on

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

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

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

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

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

Hello, I have been struggling as of late to successfully configure a pci passthrough using libvirt with kvm. Hoping someone can shed some light on the problem. Overall my experience with virtualization limited is so please forgive. The guest runs fine till passthrough is configured. I am using virt-manager. This has been tried on both a Fedora17 x86_64 and Arch Linux x86_64 build with pretty much

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

On Thu, Sep 3, 2015 at 2:29 AM, Robert Nichols <rnicholsNOSPAM at comcast.net> wrote: > 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

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