Re: Libvirt resume guest startup issues centos 7

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



> -----Original Message-----
> From: Gordon Messmer
> Sent: Tuesday, September 01, 2015 5:15 PM
> 
> On 08/31/2015 03:51 AM, Jason Pyeron wrote:
> > journal: internal error: process exited while connecting to monitor:
> > ((null):1937): Spice-Warning **: reds.c:3036:reds_init_socket:
> > getaddrinfo(127.0.0.1,5900): Address family for hostname 
> not supported 
> > I feel like this is an issue of libvirt starting before networking
> 
> I've looked at this a bit... But, bear in mind that I don't 
> use Spice, so everything I say may be wrong.

Same *exact* error with VNC.

> 
> I don't think libvirtd is starting before networking, 
> regardless of the service.  However, if you'd like to test 
> that theory, you can copy 
> /usr/lib/systemd/system/libvirtd.service to 
> /etc/systemd/system and edit it.  Replace the line 
> "After=network.target" with "After=network-online.target", 
> then reboot.  See if that affects the problem in any way.
> 

Will try, but not until Wednesday / Thursday PM.


> The problem looks vaguely like the server is trying to use an 
> IPv4 address (127.0.0.1) and an IPv6 address family.  I'm not 
> sure why it would do that.  Were there any specific 
> directions you followed to set up Spice?


Dell PowerEdge 2970
=====================
Install Centos 7 x64 minimum.
[left as default]
vi /etc/sysconfig/network-scripts/ifcfg-eno1
[change onboot=yes]
service network restart
yum update -y && yum install nano logwatch ntpd ntpdate && reboot
nano /etc/hostname
yum group install 'Virtualization Host'
chkconfig libvirt-guests on
yum install virt-manager xauth
nano /etc/sysconfig/network-scripts/ifcfg-br0
[delete auto created virtbr0]
Reboot
[create vm with defaults - centos 7 x64 minimal]
virsh autostart centos7.0
[reboot]
[debug, pull out hair, email centos list, remove ipv6, remain puzzled]


> 
> > https://bugzilla.redhat.com/show_bug.cgi?id=721350
> 
> I don't think this bug is relevant, as it results in a return 
> value of EAI_NONAME.  In your case, getaddrinfo returns EAI_FAMILY.

This and its linked tickets is where I figured to disable IPv6.

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux