Yes, for sure. EOL is EOL. Hopefully to some extent, the only other side benefit of the thread here, is that google indexing will find it, and if someone else is in the same boat in a few months they will find this discussion possibly / see the...
I see the issue. it also affects the other direction with your particular config as far as I can tell. given that PVE 8.x is EOL, it won't be fixed there. but explicitly marking your containers as privileged on the source side before attempting...
Yes, for sure. EOL is EOL. Hopefully to some extent, the only other side benefit of the thread here, is that google indexing will find it, and if someone else is in the same boat in a few months they will find this discussion possibly / see the...
I had to disable driver signing enforcement with
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit /set TESTSIGNING ON
after that, I was able to install the virtio 302 drivers... with help from Driver Store Explorer to clean up the old...
FWIW, in general migrating from a newer version to an older is always best effort, and in particular if you use newly introduced features might not be possible. the other direction should of course work (but is broken and will be fixed for this...
I can't answer all your questions, but I might be able to fill in some of the gaps...
I've written a simple HOWTO on this topic here:
https://forum.proxmox.com/threads/cloud-init-f%C3%BCr-linuxvms-ganze-einfach-unter-proxmox-ve.181926/
My post...
Adding to fireons comment I would like to add this: At my place of work I spent the last three weeks creating new vm templates (although we are running vmware but cloud-init isn't that different there). Since I needed to fullfill some special...
Hi,
Before removing any packages, please post the output of the following commands:
bootctl status
ls -R /boot/efi/EFI
dpkg -l | grep -E 'systemd-boot|grub|proxmox-boot'
findmnt /
lsblk -f
This should help confirm which bootloader is actually...
Apologies - there's a lot of text coming up:
user@proxmox:~# bootctl status
systemd-boot not installed in ESP.
System:
Firmware: n/a (n/a)
Firmware Arch: x64
Secure Boot: enabled (user)
TPM2 Support: yes
Boot into FW: supported...
Hi, OK. Thank you for confirming. I think the distinction between "Unpriv: NO" setting in the GUI (ie, this is how it is now) vs trying to flag it as "PRIV: YES" is maybe not entirely clear. But bigger picture, I agree, these are old containers /...
I can't answer all your questions, but I might be able to fill in some of the gaps...
I've written a simple HOWTO on this topic here:
https://forum.proxmox.com/threads/cloud-init-f%C3%BCr-linuxvms-ganze-einfach-unter-proxmox-ve.181926/
My post...
OK! thank you. Generally I don't use ZFS most of the time. Rather I'm working with vanilla ext4 /var/lib/vz mounted filesystem for my VM/LXC storage.
so I get the feeling my migrations will be non-sparse-aware (I think). So goes life. I think I...
Try finding if the hv- flags are actually being passed at the time of VM start, with:
qm showcmd <vmid> | grep --color "hv_"
Then you could probably remove them from the args (if present) or explicitly enter them in the args (with the - flag) to...
Does the journal show you something If you open the syslog page in the WebUI?
journalctl -f
Then open syslog in the PMGs WebUI.
...Browsercache has already been emptied for a test?
The permissions on the syslog file might also be helpful:
ls...
Try finding if the hv- flags are actually being passed at the time of VM start, with:
qm showcmd <vmid> | grep --color "hv_"
Then you could probably remove them from the args (if present) or explicitly enter them in the args (with the - flag) to...
Hi Fabian, thank you for this reply. Greatly appreciated. This makes sense that the VM are left locked on Source/Target. I think here I just have a learning curve about how PDM works. So that is good!
In terms of the original issue, and some...
Due to multiple nested-virt security-related issues, I've disabled nested virt in my proxmox nodes and was surprised by some VMs not starting after this.
All VMs have this in common:
1. Host cpu is 2x Xeon Gold 6244
2. Nested-virt disabled in PVE...
Given that there are this many checksum errors in the “data,” I don't think there's any chance that it was just free space.
You should stop using TrueNAS ZFS on ZFS on HW RAID.
If you have a backup, you should restore it.
CKSUM
9.15M
18.3M