Ich freue mich für Dich dafür, dass du keine Probleme hast.
Leider ist es so, dass es bei mir Probleme gibt.
Keine Ahnung was an der 950 anders ist als an der 750.
Trotzdem, danke für die Rückmeldung.
Hallo Forengemeinde, Neuling hier,
ich habe mir so einen Chinakracher gekauft (eine Nic, 32 GB RAM, SSD 1 TB), um damit erste Gehversuche mit Proxmox zu wagen. Im ersten Schritt konnte HomeAssistant problemlos installiert und zum laufen gebracht...
The greatest mistake one can make is to try and forklift VMware into a Proxmox environment.
You will forever be chasing your tail trying to get Proxmox to 'work' the same as VMWare.
Start the process with a clean Proxmox install and then look...
Because it is a cluster file system like VMFS, multiple nodes can access the same disk.
Since there is no such file system, multiple nodes cannot access the same disk.
If that is a requirement, you can simply continue using VMware.
*I have...
because that is how it works. as @leesteken already said, 7.0 is "just another new kernel", which happens to have a different major release number.
the order is "test", then "no-subscription" and then eventually "enterprise" after enough feedback...
For the Linux kernel version 7.0 is not more special (or a bigger change) than 6.20 would be compared to 6.19. And the jump from 6.17 to 7.0 is similar to 6.14 to 6.17.
PVE 9.x has indeed seen more than one kernel version already: 6.14, 6.17...
For the Linux kernel version 7.0 is not more special (or a bigger change) than 6.20 would be compared to 6.19. And the jump from 6.17 to 7.0 is similar to 6.14 to 6.17.
PVE 9.x has indeed seen more than one kernel version already: 6.14, 6.17...
Thanks everyone for the comments. It seems the only way to get all the features above is to use NFS. Guess we will need to use NFS going forward.
Seems that ZFS over iSCSI is a way to accomplish all the above, but the storage does not do ZFS, so...
because that is how it works. as @leesteken already said, 7.0 is "just another new kernel", which happens to have a different major release number.
the order is "test", then "no-subscription" and then eventually "enterprise" after enough feedback...
Which is what I did eventually, but my question - why no-subscription jumps a major kernel version? I can understand doing this on the test repo, but on no-subscription?
you have different CPUs, so you can't (reliably) use cputype host and live migration - you need to either switch to a different CPU type, or use offline migration.
I've just recently started backing up a couple of windows 11 PCs and this seems to be the case.
The host will freeze for the whole backup. A couple of times the host will allow RDP login / password but will then never display the desktop and...
7.0 is the new default kernel on no-subscription, but you can easily pin an older kernel with the proxmox-boot-tool.
the node will then boot with whatever kernel you pin until you remove the pin, even if a newer kernel is installed.
Late friday I decided to upgrade my proxmox 9.1.
I'm using the no-subscription repo, none of the nodes has test repo enables.
Imagine my surprise when the update decided it's time to jump to kernel 7.0 and not remain on the 6.x
At the moment...
After figuring out I had a bad patch cable with my previous reply I've had no further problems. I'd be looking at the mikrotik switch. When I had one of those I had no end of issues with it behaving poorly.