Thanks for your answer.
It turns out that I admitted a bit too fast that the agent was running
and your question made me refocus on it. I reread the PR, especially
the systemd part I tend to skip as I get tired of learning yet another
protocol/configuration. Turned out it had some conditions that when
removed made the whole thing worked !
+ systemd.services.qemu-guest-agent = {
+ description = "QEMU Guest Agent";
+ bindsTo = [ "dev-virtio\\x2dports-org.qemu.guest_agent.0.device" ];
+ after = [ "dev-virtio\\x2dports-org.qemu.guest_agent.0.device" ];
So thanks for the hint :D
>> virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive
>> file=/var/lib/libvirt/images/nixops-0084610a-4150-11e8-aef5-309c233b770e-server.qcow2,format=qcow2,if=none,id=drive-ide0-0-0
>> -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
>
> Why do you use IDE instead of VirtIO? IDE is slow and if the guest OS is
> linux it most likely has VirtIO drivers.
I use linux/nixos. The command is generated but thanks for the advice,
I might fix this later.
Cheers !
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
