Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 551578

Summary: app-emulation/virt-manager-1.2.0 When opening graphical console for a domain: '<hostname>' does not appear to be an IPv4 or IPv6 network
Product: Gentoo Linux Reporter: Guido Winkelmann <guido-genbugs>
Component: Current packagesAssignee: Virtualization Team <virtualization>
Status: RESOLVED OBSOLETE    
Severity: major    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Guido Winkelmann 2015-06-09 15:46:42 UTC
When opening the graphical console for a running domain, the following error message appears and virt-manager fails to bring up the grapical console:

'<hostname>' does not appear to be an IPv4 or IPv6 network

With <hostname> being the hostname (including domain) through which I connected to the hypervisor.

Reproducible: Always

Steps to Reproduce:
1. Open virt-manager
2. Connect to a remote libvirtd with qemu+tls://
3. Double-click on a running domain to open its graphical console
Actual Results:  
An error message as described above appears, the graphical console window shows "The console is currently unavailable".

Expected Results:  
The domain's virtual framebuffer should be shown in the graphical console window.

This appears to be the same problem as reported on the RedHat bugtracker here: https://bugzilla.redhat.com/show_bug.cgi?id=1219023

Applying the patch proposed by Giuseppe Scrivano solves the issue for me.
Comment 1 Matthias Maier gentoo-dev 2015-07-10 09:26:42 UTC
Version 1.2.1 contains bug fixes for a bunch of IPv4/IPv6 related connection problems. Please test 1.2.1 whether it still contains this issue.
Comment 2 Guido Winkelmann 2015-07-10 16:04:02 UTC
> Please test 1.2.1 whether it still contains this issue.

The problem no longer occurs with 1.2.1.
Comment 3 Matthias Maier gentoo-dev 2015-07-10 16:21:52 UTC
(In reply to Guido Winkelmann from comment #2)
> > Please test 1.2.1 whether it still contains this issue.
> 
> The problem no longer occurs with 1.2.1.

Perfect! I've removed 1.2.0  from the tree.