This thread is primarily about this bug [0]. A fix for it is available in the repositories. It’s important to boot into the new kernel, use the latest QEMU version, and configure the machine version to the latest one. This should resolve bug [0]...
I would strongly take a look onto your disks and raid system under the xfs as cannot write or read chunks are followon errors to xfs and even then to pbs.
Following links are propably of interest:
Smoother migration for WindowsVMs: https://forum.proxmox.com/threads/a-small-game-changer-for-windows-migration-to-proxmox.181582/ This is especially useful for migrations with minimal downtime as...
.
As mentioned in the Serial Terminal wiki [0], you can configure a VM's serial console to listen on a local TCP port instead of the default socket:
By doing this, the Proxmox VE host exposes the VM's serial console through a raw TCP socket...
Das ist der Beweis dafür, dass es doch blöde Fragen gibt. Gleich im allerersten Beitrag. Respekt.
Nebenbei: Ich suche ein Limousine für den eleganten Opernbesuch, möchte aber auch 2t Beton transportieren.
The UI is consistent in itself.
I also know what the meta line means, I wanted to include it just to show that the VM was already created with version 11 (and recently).
The mismatch is between what the UI (which in itself is consistent) shows...
.
As mentioned in the Serial Terminal wiki [0], you can configure a VM's serial console to listen on a local TCP port instead of the default socket:
By doing this, the Proxmox VE host exposes the VM's serial console through a raw TCP socket...
The UI is consistent in itself.
I also know what the meta line means, I wanted to include it just to show that the VM was already created with version 11 (and recently).
The mismatch is between what the UI (which in itself is consistent) shows...
Following links are propably of interest:
Smoother migration for WindowsVMs: https://forum.proxmox.com/threads/a-small-game-changer-for-windows-migration-to-proxmox.181582/ This is especially useful for migrations with minimal downtime as...
Okay, so the UI has a specific version set. Does it not look like this when you go into changing the machine type?
Also, this line: `meta: creation-qemu=11.0.0,ctime=1784036198` has nothing to do with the machine type, it's the QEMU version the...
Tatsächlich werden die VMs auch ab und zu mal Verschoben für Neustart der Nodes und dadurch entsteht eine Rotation in den VM/Node Besetzungen..
Daher kann ich die Storages nicht Node Abhängig aktivieren.
Aber der Feature-Request ist ne idee...
Hi,
We are trying out a Proxmox setup and are currently running two hosts with VE 9.1
The hosts are both Dell Poweredge 640:
56 x Intel(R) Xeon(R) Gold 5117 CPU @ 2.00GHz (2 Sockets)
and
80 x Intel(R) Xeon(R) Gold 6248 CPU @ 2.50GHz (2 Sockets)...
Following links are propably of interest:
Smoother migration for WindowsVMs: https://forum.proxmox.com/threads/a-small-game-changer-for-windows-migration-to-proxmox.181582/ This is especially useful for migrations with minimal downtime as...
Yes, we had this kind of setup running for years and started with PVE 3.4
I'm unfamiliar with MSA 2060, but if it has a dual controller setup and you're using either DA FC or two FC switches, it should be fine
Yes, for a couple of major...
I will answer here since this is the original thread. Please avoid creating duplicate threads for the same topic.
Q1
The described configuration looks good and should be fine for production.
If you haven't already,ensure to check the wiki...
Currently preparing PVE 8.4.19 single node for an upgrade to 9.
But I'm having an issue where the bootloader defaults to "Reboot into firmware interface" instead of any other valid boot entry. I have to manually select an entry each time to...
I think the main issue with adding such a feature to the API would be that anybody who can do system upgrades basically gets "root" powers. So if your compilance requirements are that you need to limit the potential breakage done by a single...
I have understood that but that does not explain the discrepancy between the CLI and API reporting version 11 while the UI shows 5.1
(or I have some giant misunderstanding - in that case please explain)
When you don't set a specific Machine Version (the GUI calls this Latest) then you get the latest when the VM is started. The version is not saved in the configuration and can only be known once the VM starts on a particular node in the cluster...