[6.5.0] VM Manager on stopped after VM reboot triggered

3 posts in this topic Last Reply

Recommended Posts

[1]Description: VM Manager is stuck to the Status "Stopped", VM Tab is empty and Libvirt Log shows this.
2018-03-30 21:51:52.454+0000: 7132: info : libvirt version: 4.0.0
2018-03-30 21:51:52.454+0000: 7132: info : hostname: HomeServer
2018-03-30 21:51:52.454+0000: 7132: error : virNetSocketNewListenTCP:343 : Unable to resolve address '' service '16509': Address family for hostname not supported

[2]How to reproduce: Restart of my Windows Server 2012 R2 VM

[3]Expected results: The VM should restart normally. 

[4]Actual results: The VM Manager switched from Running to Stop and no VM is availlable.

[5]Other information:The firsttime it happend the Error could be fixed by renaming the Server. The secondtime I could not fix the Issue with this method. Diagnostic Files are in the Attachment.


Link to post

This is the problem

Mar 30 14:51:52 HomeServer root: /usr/sbin/libvirtd: error: Unable to initialize network sockets. Check /var/log/messages or run without --daemon for more info.

  Not sure however what to do to fix it.

Link to post

But this knowledge was great, I was able to fix it by changing the network card. And is there a known Issue with Intel network cards? Because my Mainboard has a Giga PHY Intel® I218V   Network adapter and there is a known Issue with Windows Server 2012 and the driver for it.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.