What’s the best practice to group vm guests in virt-manager?

I run a lot of vm-guests on a host and manage they with wirt-manager. Whats the best practice to group them for a better overview? Best: independ on the guest names

I figure out a good way is to use the title field, i.E.

  • “[MAILSERVER] Mailserver_A”
  • “[MAILSERVER] Mailserver_B”
  • “[WEBSERVERS] Webserver_A”
  • “[WEBSERVERS] Webserver_B”

But are there other/better options?

18.04 – Virt-Manager: Spice/VNC monitor doesn’t work

The SPICE/VNC monitor that appears whenever a VM is clicked on in virt-manager is now broken for me. Whenever that window is called, a message briefly appears saying:

Error connecting to graphical console: Failed to recv file descriptor: Permission denied 

KVM-QEMU will then disconnect from virt-manager. I can double-click to reconnect and click on the VM to duplicate the effect. This has no effect on the underlying VM, which continues to run and be accessible via virt-viewer.

Additionally, whenever I open a VM and get the SPICE/VNC screen, libvirtd will throw the following error. I’m not sure if its related or not:

1712: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error 

I have done the following things to attempt to solve this problem:

  • Disabled Apparmor (temporarily)
  • sudo virt-manager
  • Configure libvirtd to use root/root.
  • Confirm my username is added to libvirt and libvirt-qemu
  • Purge all relevant packages and reinstall.
  • sudo chmod 0777 VM-file

It doesn’t stop me from using the VMs, but its highly annoying that this problem cropped up at random (following a power outage), and I’d like to figure out what the hell happened so I can correct it. Anyone have any ideas how I can fix this?

virt-manager does not show vnc machines but virt-viewer is working fine

virt-manager (1.32) stops to show the guest screens but virt-viewer is working fine.

When I issue a virt-viewer command, I got the guest screeen:

virt-viewer –connect=qemu+ssh://supervisor@192.168.0.21/system Linux22

But when I call from virt-manager, the guest screen is blank and do not accept keyboard commands either.

How can I fix virt-manager or get debug info?

virt-manager vm console requires password

I have just started learning foreman. I added a KVM host to the foreman as a compute resource.

I can now provision VMs from foreman now but I cannot view the console of the VMs that are provisioned from foreman as I am prompted for a password.

Console requesting password

I am now sure what is requesting this password? I search for a couple of days but did not find any related posts.

Cheers, J

virt-manager vm console requires password

I have just started learning foreman. I added a KVM host to the foreman as a compute resource.

I can now provision VMs from foreman now but I cannot view the console of the VMs that are provisioned from foreman as I am prompted for a password.

Console requesting password

I am now sure what is requesting this password? I search for a couple of days but did not find any related posts.

Cheers, J

KVM’s Virt-Manager is not able to PXE boot KVM machines from MAAS Server

I am using virt manager for deploying maas on kvm and other maas nodes for openstack cloud and juju controller running on those KVMs in a dediated single server. For that purpose i have made 2 networks one is br0 attached with eth0 (physical interface) for maas public access and other is “isolated private network” for maas nodes. i have attached my maas-server running on one of the kvm with these two networks by making 2 interfaces (i.e public and private). Now i am trying to PXE boot juju controller machine from MAAS private network but it does not pxe boot that machine and instead giving an error “No bootable device”. Why this is happening? MAAS is supposed to builtin provide a dhcp and tftp server but juju controller is not able to pxe boot fom MAAS server.. Do i need to configure my network ?? Kindly help

I deleted the Libvirt user, and now virt-manager throws `Unable to connect to libvirt qemu:///system.`

I understand this wasn’t smart, just looking to find out how to fix it.

Full error message:

Unable to connect to libvirt qemu:///system.  Verify that the 'libvirtd' daemon is running.  Libvirt URI is: qemu:///system  Traceback (most recent call last):   File "/usr/share/virt-manager/virtManager/connection.py", line 1036, in _do_open     self._backend.open(self._do_creds_password)   File "/usr/share/virt-manager/virtinst/connection.py", line 144, in open     open_flags)   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 104, in openAuth     if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory