Der vollständig halber halt, hier meine VM-Config von einem (aktuellen) Windows Server 2003. Vielleicht hilft dir das ja.
boot: order=ide0;ide2;net0
cores: 4
cpu: x86-64-v2-AES
ide0: SSD-vmdata:vm-121-disk-0,size=32G
ide2: none,media=cdrom...
Es gibt hier ein Best Practices Artikel. Die Ausgabe von qm config VMID oder ein Bild von Hardware wäre hilfreicher als diese vielen zu stark gecroppten Screenshots. Gibt es einen guten Grund dass du VirtIO Block gewählt hast?
Soweit ich das sehe...
Hmm. Bei meiner LVM Installation ist das nicht. Möglicherweise eine Eigenart des Installers oder es wurden manuell Werte gesetzt. Ich habe sonst keine Erklärung.
Ich hätte da eine Theorie:
Laut deinen bisherigen Beiträgen sind "485.3M" übrig/ungenutzt.
Das enspricht nach Umrechnung so ziemlich genau 473 MiB.
Also (( 485.3M * 1000 ) / 1024).
Und siehe da, das Laufwerk meldet eine Größe von "238.47 GiB"...
If you have not seen these articles yet, you may find them useful in your research:
https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage
https://kb.blockbridge.com/technote/proxmox-qcow-snapshots-on-lvm...
VMware enables this behavior because it has VMFS - a cluster-aware, shared filesystem. VMFS implements proprietary on-disk locking and reservation mechanisms that safely coordinate multi-initiator access to the same disk.
Proxmox does not...
You cannot have Shared storage in a two node non-cluster installation. Shared storage, as defined by PVE terminology, is part of the cluster.
Everything you do after that is a road to data corruption. There are coordinated operations...
HEre i
His first screenshot in the opening post shows migration from node2 to node6, with LUN92 involved. It is not available to node6
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Yeah I get you, but he has "MD3200" luns to all 5 nodes. if he's not mapping some to all WWNs thats by choice, not by limitation. I suppose those could be different physical devices.
I saw "6 pve" and inverted it to "pve 6". Nevermind... it was an interesting side adventure :-/
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
You are running an OLD (unsupported) version of PVE. In fact, as of today Proxmox dropped the repository to support Buster.
The code that generated the error you provided is different, improved, in newer versions...
When you migrate from pve2 to 6, you will need to specify store on the destination- but why do you limit node access when all 5 nodes can see the storage?
Your understanding is correct. @alexskysilk covered the "node" restriction that I think is missing in your case.
If you have proper shared storage that is available to nodeA and nodeB - migration is an act of moving VM state and re-assigning...
If you mark a storage pool as shared, PVE will assume its available on all nodes by default (there is an option to limit to specific nodes, but you need to set those)
If a "shared" pool doesnt exist on the destination, the migration will...
apt-get update does not make changes to the system. It only refreshes the information about available packages, so it cannot be the cause.
Glad to know that you found a work-around to boot. Maybe /etc/default/grub got corrupted (can you show that...
Yes but the enterprise repository is slightly behind the latest updates which it gets in batches. All features and fixes are available for free (with source code) on the no-subscription repository (immediately as soon as they are pushed there...
Depends on how one "stumbles" into learning about no-sub repo...
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Enjoy PVE and see you in a few weeks when you come back with "my GUI stopped working and I did not change anything".
This is based on the fact that you:
- informed us that you are not an Enterprise subscription user in the now deleted post
-...