This will go through the normal release cycle and at the end will be available via the enterprise repository. Can't give you an exact date, but in the next weeks probably. Regarding your nfs server, I would debug the stack e.g. network, DNS etc. do some tests with iperf for example, check your...
Yeah that's because it is not checked if there is actually a file, it just generates the path for that storage. I just wanted to make sure that the path is generated correctly, but this shouldn't happen when not called directly as it is checked at a higher level.
I still think that the...
Ok, can you please check if you can see any error when using the mentioned cli commands.
/usr/bin/qemu-img info <path-to-qcow2>
pvesm path <volumeid>
I know this is a little bit tedious, but this seems to be very inconsistent behavior from what you reported.
Please give it a try a few times or...
Ok the size is wrong here, because it should be already the absolut new size and still is 20GB.
So it seems the initial idea is still correct, the disk size can't be read, so let's check were this all starts. We'll need to add some more debug info.
Same procedure as before, but other file.
Ok, looks good.
Yeah that's expected, as we didn't tell proxmox anything about it.
Next step would be to add some debug printing to the actual code to see what's happening here, when executed via the management interface.
Open the file /usr/share/perl5/PVE/QemuServer.pm and locate the "sub...
Ok great, we are getting closer to the actual problem.
Let's do some manual resizing to see what actually cause this.
First connect to the problematic VM with ssh.
tail -f /var/log/syslog
Keep it that way and monitor whats happening while we do the resize.
Now on the host:
The no backup option has really nothing to do with this context. AFAIK this isn't even evaluated when cloning or resizing.
You can force a rescan of the storage with:
qm rescan --vmid <integer>
Sure here are our offerings: https://www.proxmox.com/en/proxmox-ve/pricing
Ich würde Ihnen empfehlen, nichts auf dem Host zu installieren was nicht unbedingt notwendig ist und schon gar nicht . Ich verstehe nicht ganz wieso Sie die 3 Nodes nicht einfach zu einem Cluster zusammenfassen? Die Applikation wird doch in einer VM laufen insofern wäre Migration allein schon...
Please take a look on general debian network configuration, there is an example on how to set an mtu which should point you in the right direction.