Alvin,
Thanks for that. I disabled the xendomains service (I had to do it
twice, as it seemed to re-enable itself after the first reboot) and it
now starts libvirtd automatically on startup.
However, all is not well!
"xl list" and "virsh list" will just hang
"systemctl stop libvirtd" just
Jim:
Try systemctl disable xendomains.service
It is conflicting with libvirtd.service.
I found it by using
"systemd-analyze dot libvirtd.service | dot -Tgif > /tmp/dot1.gif"
On 07/26/2017 10:19 AM, Jim Fehlig wrote:
On 07/26/2017 04:46 AM, G Crowe wrote:
Jim,
Thanks for that, I had
Please configure your mail client to send plain-text version to mailing
lists ...
On Tue, Jul 25, 2017 at 16:08:58 +0100, Dirty Dan wrote:
> How can I automatically revert to a snapshot after the guest
> is stopped?/etc/libvirt/hooks/qemu
#!/bin/sh
name="$1"
action="$2"
if [ "$name" = "name" ];
[off topic]
One day someone had the idea to test a disaster scenario and plugged the
power supply on the server that guarded the security doors. All went quite
well until that someone wanted to enter the server room to power on that
server again. At this moment he noticed that the doors would no
libvirtd is not started by systemd on my f25 laptop
so this may not be xen related.
On 07/26/2017 10:19 AM, Jim Fehlig wrote:
On 07/26/2017 04:46 AM, G Crowe wrote:
Jim,
Thanks for that, I had manually installed
libvirt-daemon-driver-xen, but also needed to install
I believe this problem also exists in F25.
There are upsides to having a vm do the networking and I have used that
scheme for something like a decade.
The point is that libvirt should start up and start its VM's correctly.
If you cannot depend on the system starting correctly then very
On 07/26/2017 04:46 AM, G Crowe wrote:
Jim,
Thanks for that, I had manually installed libvirt-daemon-driver-xen, but
also needed to install libvirt-daemon-driver-libxl. I can now create VMs and
convert config formats.
However the daemon still fails to start on bootup. It starts fine
Note that this does not help with the original problem but points out a
critical design flaw.
To me your it infrastructure design has no working disaster recovery plan.
You should always be able to access critical functionality and from there
be able to restore complete functionality step by
Jim,
Thanks for that, I had manually installed
libvirt-daemon-driver-xen, but also needed to install
libvirt-daemon-driver-libxl. I can now create VMs and convert config
formats.
However the daemon still fails to start on bootup. It starts fine when I
manually start it with "systemctl
