Ubuntu
libvirt package

Domains don't start automatically after reboot a parent host

Bug #681703 reported by korobass
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Expired
Low
Unassigned

Bug Description

When I reboot my parent machine, virtual machines don't start automatically.

ls /etc/libvirt/qemu/autostart/
sw3.xml tm-xp.xml

Syslog complaining:
Nov 26 07:20:00 zyrafa libvirtd: 07:20:00.479: warning : qemudDispatchSignalEvent:385 : Shutting down on signal 15
Nov 26 07:21:21 zyrafa libvirtd: 07:21:21.448: warning : qemudStartup:1087 : Unable to create cgroup for driver: No such device or address
Nov 26 07:21:25 zyrafa libvirtd: 07:21:25.478: error : qemuMonitorCommandWithHandler:240 : cannot send monitor command 'info chardev': Connection reset by peer
Nov 26 07:21:25 zyrafa libvirtd: 07:21:25.478: error : qemuMonitorTextGetPtyPaths:1704 : operation failed: failed to retrieve chardev info in qemu with 'info chardev'
Nov 26 07:21:25 zyrafa libvirtd: 07:21:25.591: error : qemuAutostartDomain:584 : Failed to autostart VM 'tm-xp': operation failed: failed to retrieve chardev info in qemu with 'info chardev'
Nov 26 07:21:55 zyrafa libvirtd: 07:21:55.530: error : qemuMonitorOpenUnix:268 : monitor socket did not show up.: Connection refused
Nov 26 07:21:55 zyrafa libvirtd: 07:21:55.530: error : qemuConnectMonitor:822 : Failed to connect monitor for sw3
Nov 26 07:21:55 zyrafa libvirtd: 07:21:55.642: error : qemuAutostartDomain:584 : Failed to autostart VM 'sw3': monitor socket did not show up.: Connection refused

Each virtual machine complaining to virtual machine log file:
getaddrinfo(127.0.0.1,5900): Name or service not known

Then if I start machines manually in virsh or virt-manger, they start without any problem

Any suggestions ??

korobass (korobass)
Changed in libvirt (Ubuntu):
assignee: nobody → korobass (korobass)
Revision history for this message
Chuck Short (zulcss) wrote :

Which version is this with? Also dont assign bugs to yourself if you dont inted to provide a fix for it.

Changed in libvirt (Ubuntu):
assignee: korobass (korobass) → nobody
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
korobass (korobass) wrote :

Ok I'm sorry for assign bug to myself, I don't think that I could provide any fix for this issue.

I have problem on Ubuntu Lucid Lynx 10.04.1
on kernel:
    2.6.32-26-server
Architecture: amd64

Revision history for this message
korobass (korobass) wrote :

Source: libvirt
Version: 0.7.5-5ubuntu27

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]

Changed in libvirt (Ubuntu):
status: Incomplete → Expired
Revision history for this message
korobass (korobass) wrote :

I found solution to this issue:

This is the problem with DNS and this line from log file is a clue:

  getaddrinfo(127.0.0.1,5900): Name or service not known

DNS not working early enough during the boot .

So when some virtual machines are trying to start up, but DNS service doesn't work at this moment and they fail.

You can find more info at this mailing list:
http://comments.gmane.org/gmane.comp.emulators.virt-tools/821

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

That *should* be fixed as of 0.7.5-5ubuntu27.14. Can you show which libvirt version you are using? (dpkg -l libvirt-bin)

Although since your machine is having trouble resolving 127.0.0.1, that seems like a system problem. Can you also post your /etc/hosts file?

Changed in libvirt (Ubuntu):
status: Expired → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]

Changed in libvirt (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Adrian Bridgett (adrian-bridgett) wrote :

This is still a problem for me on Debian with 0.9.11-2 (so I suspect that it's also an issue with Ubuntu still).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.