As stated, I am not troubled, so there is no reason for me to use enterprise. I am using the Test Repository to test features I am interested in testing new features, so there is no particular reason to use enterprise.
As long as I get the same...
Es ist im no-subscription Repo, das ist genau dafür gedacht, dass solche Fehler bemerkt werden, bevor sie bei zahlenden Kunden im enterprise-Repo landen. Also: Ich sehe das Problem nicht
I have similliar poblem and I think the problem is that download.proxmox.com routes all http/https incoming traffic to enterprise.proxmox.com.
The portal asks username/password for access to download.proxmox.com via web or apt if I ignore ssl...
A more current solution would be available as follows, I presume.
1. Make a copy of the original VM file "virtualbox-vm.vdi"
2. Copy this file to the PVE environment of your choice.
3. Prpare an empty VM e.g., VM 101, at your deliberation.
4...
That's right.
I don't apply updates directly to production environments myself, but since I'm in charge of non-PVE maintenance, most people who contact me about issues in my area just go ahead and apply the updates as is. And surprisingly, there...
I think we're actually on the same page- its the meaning we take from it that is different.
"safety" in this context is the continued uninterrupted delivery of service. the SAFEST thing to do in production is LEAVE A WORKING ENVIRONMENT ALONE...
Sorry. Since I don't have the Enterprise edition, there was no way I could have known, so I deleted my previous post.
Anyone who can set up the Enterprise repository can run `apt policy pve-qemu-kvm` to see that it's not available.
*I don’t...
Trying here as my report in the kernel thread is not getting much attention. I know of at least 5 users reporting this issue here and on Reddit - but it definitely also doesn't affect everyone.
The issue is easily tested and consistently...