Hello,
I have a VM with Nethsecurity 8-24.10.0-ns.1.6.0 running on proxmox with qemu guest agent installed.
All’ works very good but when i try to reboot proxmox, Nethsecurity vm wont shutdown.
I have to kill the machine manually to complete reboot procedure.
When proxmox boot again, all works correctly.
Anyone has my problem with shutdown command to Nethsecurity vm?
Thank you.
Here are no issues when rebooting Proxmox 8 nodes with running NethSec VMs. Do you use Proxmox 9?
Did you also enable it in Proxmox VM options?
I don’t use the qemu agent for NethSec, does it help to disable it?
Hi @sarz4fun,
I also use nethsec on proxmox and I don’t have a problem.
But, I don’t have the agent installed, how did you do it?
Thanks,
Installing the qemu agent is explained in the documentation.
Hello the problem was on 8 and now on 9.
Could be virtio store and network settings on vm the problem?
Which network/virtio settings do you use?
I’m going to try to reproduce…
Hello.
This Is my setup.
If i send reboot signal to VM, i have this message on console
[1533911.761784] traps: qemu-ga[61921 general protection fault ip:563885c533e7 sp:7ffd8307f790 error:0 in qemu-ga[563885c3…
If i reboot or shutdown from Nethsecurity, vm reboot/shutdown correctly.
I could reproduce the issue, It seems there’s a bug in OpenWRT qemu-ga, see qemu-ga: segmentation fault on VM shutdown from host · Issue #25209 · openwrt/packages · GitHub
It’s not about your virtio configuration, I could also reproduce the issue when installed as explained in the documentation (scsi0)
traps: qemu-ga[61921 general protection fault ip:563885c533e7 sp:7ffd8307f790 error:0 in qemu-ga[563885c3…
As a workaround you could disable the QEMU guest agent in the Proxmox VM options to make the shutdown work.
Amazing research!
It should be fixed with the next NethSec image update, thanks to @Tbaile for support.
Thanks @sarz4fun for pointing out the bug.
Is not a problem for me, when i Need to reboot proxmox (rarely), i will stop Nethsecurity from ui before. I can wait until the problem is fixed.
I can confirm, that in 8.7.1 it’s working again.
