On 01/19/2016 10:42 AM, Outback Dingo wrote:
On Tue, Jan 19, 2016 at 4:32 PM, Cole Robinson <crobinso(a)redhat.com
On 01/18/2016 03:05 PM, Outback Dingo wrote:
> So my environment
> Fedora 23 KDE spin
> XEN-4.5.2 and kernel 4.2.8 booted via EFI where everything works fine using
> virt-manager to manage vms under XEN, all is good.
> a recent update installed kernel-4.3.3 so i reset the xen efi configuration,
> booted got into the desktop no problems. The issue arises when trying to
> launch vms from virt-manager, it always throws a virt-manager viewer
> connection to hypervisor host got refused or disconnected.
> however, if i go back to using kernel 4.2.8 it all works fine. So there in
> lies the question, whats changed that is now preventing virt-manager from
> aunching vms properly.
> Sorry for the cross post, just trying to find the answer. thanks in advance
I suggest filing a bug against xen. See if there's any different output in
dmesg, attach /var/log/libvirt/libxl/$your-vm-name.log, attach virt-manager
--debug output when reproducing
Id be more inclined to think this is a kernel build issue and not a XEN issue,
however... filing a bug with debug data attached could be helpful.
Xen has many of its own specific bits in the kernel. Filing against the xen
component is the best way to get xen guys to take a look, they will move it to
the kernel if necessary.