Fedora 23 KDE spin / XEN / virt-manager and vmlinuz-4.3.3-301.fc23.x86_64

[Outback Dingo]

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

[JD]

On 01/18/2016 01: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

Why don't you keep booting kernel 4.2.8 until the problem is resolved, 
possibly in the next update?

[Outback Dingo]

On Mon, Jan 18, 2016 at 9:12 PM, jd1008  wrote:
> On 01/18/2016 01: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
> >
> > Why don't you keep booting kernel 4.2.8 until the problem is resolved,
>
> possibly in the next update?

well, weve had 2 kernel updates 4.3.3-300 and 301... though id prefer to
know what the problem is, and resolv it, seeing this is a skylake, id
prefer to use a later kernel then the 4.2 series.
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Cole Robinson]

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

- Cole

[Outback Dingo]

On Tue, Jan 19, 2016 at 4:32 PM, Cole Robinson  wrote:
> 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.
> Cole
>
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Cole Robinson]

On 01/19/2016 10:42 AM, Outback Dingo wrote:
> On Tue, Jan 19, 2016 at 4:32 PM, Cole Robinson <[e-mail]
> > wrote:
> 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.

- Cole

[Bill McGonigle]

On 01/18/2016 03:05 PM, Outback Dingo wrote:
> 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.

If you were trying to launch more than 7 DomU's, you might have hit the
problem I did, which seems to be recently fixed:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810472
 https://lkml.org/lkml/2015/12/16/455

Symptom was:
libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get
dompath for 8: Bad file descriptor

I haven't verified that this patch went into
kernel-4.3.5-200.fc22.x86_64 in -testing, but it works for me when 4.3.4
caused all the xl tools to fail on creation of Dom #8.

4.3.3-4 only seem to work for seven Dom's or fewer.

-Bill