Quoting Franck78 (495...@bugs.launchpad.net): > well, > if it is not "/var/something" > there is also > "/dev/pts" > > Something is wrong around the "qemuMonitor" routines. > > find why qemuMonitorIORead:487 is triggered and the bug is closed !
Libvirt's monitor is trying to read from already-opened monitor fd. Qemu has crashed, perhaps unable to find some backing store, perhaps for some other reason. /var itself is ok - even it it had gotten overmounted, libvirt is reading from an fd and the overmount wouldn't matter. We need to figure out why qemu crashed. There may be useful info in /var/log/libvirt/qemu/ipcop-clone.log > I really don't understand the logic of 'upstart' to trace into it, sorry. > Openning a new bug on the same subject ? Why ? Because yours has a different cause, and is therefore a different bug with similar symptoms. Globbing the info with that from other bugs makes it harder to cleanly reason about it and minimizes our chances of finding the root cause. ** Summary changed: - autostart almost always fails on boot time host + autostart fails on boot time host when network devices not ready -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/495394 Title: autostart fails on boot time host when network devices not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/495394/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
