You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I setup a Windows 11 VM following https://ubuntu.com/tutorials/how-to-install-a-windows-11-vm-using-lxd which worked fine.
Sometimes I can't shutdown the vm using lxc stop wm11test.
After some testing I noticed that with lxc start win11test && sleep 260 && lxc stop win11test or lower sleep times starting and shutting down the vm works. Using a time >= 300 like lxc start win11test && sleep 330 && lxc stop win11test it seems like Windows doesn't get or react to the shutdown request. (I can still connect to the vm and shut it down manually.)
Here's what I see using lxc monitor --pretty:
Using Ubuntu 22.04.5 LTS (5.15.0-130-generic) with lxd from snap
I setup a Windows 11 VM following https://ubuntu.com/tutorials/how-to-install-a-windows-11-vm-using-lxd which worked fine.
Sometimes I can't shutdown the vm using
lxc stop wm11test
.After some testing I noticed that with
lxc start win11test && sleep 260 && lxc stop win11test
or lower sleep times starting and shutting down the vm works. Using a time >= 300 likelxc start win11test && sleep 330 && lxc stop win11test
it seems like Windows doesn't get or react to the shutdown request. (I can still connect to the vm and shut it down manually.)Here's what I see using
lxc monitor --pretty
:Startup works fine, but no response to the shutdown request. I first thought this might be an issue with older virtio drivers, so I installed https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.266-1/virtio-win-0.1.266.iso and restarted the VM, but that didn't help either.
When it's working (smaller sleep timer), one can see a reply a few seconds later.
When it's not working it runs in the 10 minute timeout:
Am I missing something? Should I install something? Is it a bug? Is there way to specify the fail timeout (10min)?
The text was updated successfully, but these errors were encountered: