Unfortunately it starts at the boot it did after the host went unresponsive.
I tried a live migrate from one host to another, they are exactly the same hardware. The vm was a win 10, 8 core kvm cpu, 8 GB ram, virtio storage (on nfs), e1000 nic. I have done this loads of times before and it...
I did a apt autoremove to get just a bit of disk space available, I could then run a check of what folders was the biggest. it was actually loads of GB in kern.log , messages and syslog (29 GB in each)
I moved one vm from one host to another and the vm became immediately non responsive. After a few more minutes the proxmox host also became unresponsive and restarted itself. When it restarted the local storage had gone up to 100%
The VM in question got is qcow file in an external file...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.