I am not sure if this is a libvirt or libxl problem.
It looks as if each running vm has an associated event thread and this
thread calls the libxl_destroy to clean up the rebooting processes.
Possibly these threads should lock to insure synchronization and allow
only one reboot or termination a
On Fri, Oct 31, 2014 at 08:34:48AM -0400, Alvin Starr wrote:
I was sort of hoping that is was something simple like setting the
"do_the_right_thing" flag.
The libvirtd kicks out
2014-10-31 11:58:57.111+: 8741: error : virRegisterNetworkDriver:549
: driver in virRegisterNetworkDriver must no
I was sort of hoping that is was something simple like setting the
"do_the_right_thing" flag.
The libvirtd kicks out
2014-10-31 11:58:57.111+: 8741: error : virRegisterNetworkDriver:549
: driver in virRegisterNetworkDriver must not be NULL
2014-10-31 11:59:29.379+: 8840: error : virReg
On Thu, Oct 30, 2014 at 01:00:04PM -0400, Alvin Starr wrote:
If I reboot a single vm through libvirt/libxl the system reboots normally.
If I have several vm's reboot at the same time then The systems go into
a paused state and do not reboot.
I then have to kill them via xl and restart them.
If I reboot a single vm through libvirt/libxl the system reboots normally.
If I have several vm's reboot at the same time then The systems go into
a paused state and do not reboot.
I then have to kill them via xl and restart them.
--
Alvin Starr || voice: (905)513-7688
Ne
