[Bug 1891092] Re: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines

2020-09-13 Thread thomas
virtual machine are not showing up in cockpit for me either.. user@1000.service Unable to open /dev/kvm: Permission denied CODE_FILE ../../../src/util/virhostcpu.c CODE_FUNC virHostCPUGetTscInfo CODE_LINE 1338 LIBVIRT_CODE38 LIBVIRT_DOMAIN 0 LIBVIRT_SOURCE util.error PRIORI

[Bug 1891092] Re: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines

2020-09-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cockpit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891092 Title: Fr

[Bug 1891092] Re: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines

2020-08-11 Thread Russell Wing
Further update...works when you use the session option to create the VM (rather than system). Horribly slow though with all the negatives of using session rather than system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug

[Bug 1891092] Re: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines

2020-08-11 Thread Russell Wing
Been testing further. Based on errors relating to apparmor tried complain mode for libvirtd followed by reboot and completely disabling apparmor. However no difference and these messages are still in the logs. Seeing this error in the log: Unable to open /dev/kvm: Permission denied CODE_FILE