Hi all,
I was testing migrating from vmware ESXi to proxmox, and what has been amazingly successful is not working in proxmox.
I have a single old desktop that I am testing out for hypervisors and want a number of services running. I was interested in LXC and several other proxmox features (especially the server linux itself is just linux not like esxi).
I was successfully able to setup things in ESXi, with guests running their own backup using 'Relax and Recover' (rear) to my NAS and tested recovery which worked as well. This was one of the ways for me to go from V2V, V2P and P2V and I've now done a few of these and it works well.
Problem I ran into:
When I create a new guest in proxmox and use a rescue ISO of one of the guests, it starts grub and then it gets stuck on a message that looks like it is trying to initialize serial tty(?) and then it says failed and it hangs indefinitely.
Note that this behavior is not there when running the same iso in ESXi or in physical node.
I have tried a few things:
1. added and removed serial device in guest hardware - did nothing.
2. Gemini found this for /etc/rear/local.conf to see if ttyS0 can be ignored - that too did nothing.
3. I was able to setup a serial port on proxmox and use the TAB key during rescue startup to add console=ttyS0,115200n8 then ran this
which diverted the console logs into a file.
Looking into the file I see something like this (some repeated messages but the last bit is like so):
Anyone know why rear will rescue on ESXi but not on Proxmox?
Thanks
I was testing migrating from vmware ESXi to proxmox, and what has been amazingly successful is not working in proxmox.
I have a single old desktop that I am testing out for hypervisors and want a number of services running. I was interested in LXC and several other proxmox features (especially the server linux itself is just linux not like esxi).
I was successfully able to setup things in ESXi, with guests running their own backup using 'Relax and Recover' (rear) to my NAS and tested recovery which worked as well. This was one of the ways for me to go from V2V, V2P and P2V and I've now done a few of these and it works well.
Problem I ran into:
When I create a new guest in proxmox and use a rescue ISO of one of the guests, it starts grub and then it gets stuck on a message that looks like it is trying to initialize serial tty(?) and then it says failed and it hangs indefinitely.
Code:
[ * ] Job dev-ttyS0.device/start running (XXs / 1min 30s)
[DEPEND] Dependency failed for serial-getting S0.service - Serial Getty on ttyS0Note that this behavior is not there when running the same iso in ESXi or in physical node.
I have tried a few things:
1. added and removed serial device in guest hardware - did nothing.
2. Gemini found this for /etc/rear/local.conf to see if ttyS0 can be ignored - that too did nothing.
Code:
EXCLUDE_SYMLINK+=( /etc/systemd/system/getty.target.wants/serial-getty@ttyS0.service )
Code:
qm set <VMID> -args "-chardev file,id=char0,mux=on,path=/var/log/proxmox/vm-<VMID>-console.log,signal=off -serial chardev:char0"Looking into the file I see something like this (some repeated messages but the last bit is like so):
Code:
getty@tty0.service: Failed to destroy cgroup /system.slice/system-getty.slice/getty@tty0.service, ignoring: No medium found
No filesystem is currently mounted on /sys/fs/cgroup.
getty@tty0.service: Failed to determine whether cgroup /system.slice/system-getty.slice/getty@tty0.service is empty: No medium found
getty@tty0.service: Job 70 getty@tty0.service/start finished, result=failed
[FAILED] Failed to start getty@tty0.service - Getty on tty0.
See 'systemctl status getty@tty0.service' for details.
No filesystem is currently mounted on /sys/fs/cgroup.
getty@tty0.service: Releasing resources...
[ **] Job dev-ttyS0.device/start running (1min 29s / 1min 30s)
dev-ttyS0.device: Job dev-ttyS0.device/start timed out.
[ TIME ] Timed out waiting for device dev-ttyS0.device - /dev/ttyS0.
serial-getty@ttyS0.service: Job 12 serial-getty@ttyS0.service/start finished, result=dependency
[DEPEND] Dependency failed for serial-getty…S0.service - Serial Getty on ttyS0.
serial-getty@ttyS0.service: Job serial-getty@ttyS0.service/start failed with result 'dependency'.
Startup finished in 4.733s (kernel) + 1min 30.946s (userspace) = 1min 35.680s.
No filesystem is currently mounted on /sys/fs/cgroup.
System is tainted: unmerged-usr:unmerged-bin:var-run-bad
dev-ttyS0.device: Job dev-ttyS0.device/start failed with result 'timeout'.Anyone know why rear will rescue on ESXi but not on Proxmox?
Thanks