Background; migrating VM's from ESXi/VSphere to Proxmox. Using ovftool and then qm importovf. Bit of faffing around trying to set the correct hardware before it would boot; the wiki instructs you to use sed to edit hardware options, proxmox doesn't like 'idehw' apparently.
Eventually got the machine booted and it was working fine. I've got another import running at the moment and then noticed the original VM stopped responding. A 'reset' from proxmox didn't work so tried a 'stop'. This stopped it but now it wont boot. Constantly getting "timeout waiting for systemd".
Can anyone advise what the problem might be?
Only not 'normal' situation at the moment is that qm import is currently running for another VM i'm moving over.
Eventually got the machine booted and it was working fine. I've got another import running at the moment and then noticed the original VM stopped responding. A 'reset' from proxmox didn't work so tried a 'stop'. This stopped it but now it wont boot. Constantly getting "timeout waiting for systemd".
Code:
[root@host ~]$ pveversion
pve-manager/6.2-10/a20769ed (running kernel: 5.4.34-1-pve)
Code:
root@host ~]$ systemctl status pvestatd
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-08-12 13:15:47 BST; 6 days ago
Main PID: 3209 (pvestatd)
Tasks: 1 (limit: 4915)
Memory: 72.5M
CGroup: /system.slice/pvestatd.service
└─3209 pvestatd
Aug 18 09:37:10 host pvestatd[3209]: status update time (20.243 seconds)
Aug 18 09:37:30 host pvestatd[3209]: status update time (20.239 seconds)
Aug 18 09:37:50 host pvestatd[3209]: status update time (20.215 seconds)
Aug 18 09:38:11 host pvestatd[3209]: status update time (20.258 seconds)
Aug 18 09:38:31 host pvestatd[3209]: status update time (20.227 seconds)
Aug 18 09:38:51 host pvestatd[3209]: status update time (20.266 seconds)
Aug 18 09:39:09 host pvestatd[3209]: status update time (18.174 seconds)Can anyone advise what the problem might be?
Only not 'normal' situation at the moment is that qm import is currently running for another VM i'm moving over.