Search results

Hey, I looked through the old thread and this looks strange. Are you sure the key is installed in the correct location and has the appropriate permissions? Could you check what `ls -lah etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg` and `apt-key list` output? It seems somehow apt struggles...

BTW: If you want an explainer of the differences between GPL and AGPL in more laymen's terms, the FSF has this article for you [1]. [1]: https://www.gnu.org/licenses/why-affero-gpl.html

This has already been reported and fixed [1]. The fix should be packaged with the next version of pve-manager. [1]: https://bugzilla.proxmox.com/show_bug.cgi?id=5734

So the question is, do you need a subscription for a QDevice? No, only for full nodes in a cluster. So if you have a two node cluster with a QDevice, only the two nodes need a subscription. The QDevice does not need an extra subscription.

What exactly are you worried about here? Looks fine to me :)

Nothing we provide officially, but generally CPUs of the same generation and vendor should work. Migrating from older to newer CPUs should also work in general. The other direction will likely not work unless you use a more restrictive CPU type. You can also create custom CPU types to improve...

Sorry, I can't provide anything definitive here, you might want to open a bug over at the Bugzilla [1], though. That's the preferred way of opening and tracking feature requests. [1]: https://bugzilla.proxmox.com/

In welchem Format erhalten Sie den die Daten von Azure? Je nach Storage kann das Zielformat auf Proxmox VE ein unterschiedliches sein. Auf file-based Storages können Sie entweder QCOW2 oder RAW verwenden. Wobei die beiden Formate unterschiedliche Features anbieten.

That won't work well. If you tell the VM it has 8 GB of memory, but actually only provide it with 4 GB it will likely crash or panic every time it's trying to use anything more than the 4 GB it actually has available.

Hi, we don't really support aarch64 officially, so this probably won't be fixed. However, that commit should only really be relevant for the backend. You can try to revert that commit if you just want to build the client as that change shouldn't be relevant for the client to function.

Generally we recommend only products that use the enterprise repository in a productive environment. That being said, the sync protocol we use is fairly stable and shouldn't change between minor versions. Also in that case your second PBS would only be used for a second copy, so the risks should...

Hi, I think you are trying to address multiple points here, but I'll add some piece information that might help in this discussion. First, removable datastores are planned and being worked on [1]. This would be needed to handle switching out USB drives like you describe, so maybe keep an eye on...

You should take a look at resource pools [1]. This should enable you to restrict specific users/groups to specific resources. [1]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pveum_resource_pools

Not sure what you mean by “edge”. Anyway, the problem isn't about your hardware or host support vor IOMMU/PASID, but rather that your VM does not seem to provide that. At least that's what I gather from the GitHub Issue [1]. You can try to enable vIOMMU (which emulates IOMMU for your VM), as...

I'm not sure what you expect from us. A developer of the driver gave you a clear answer in both the issues that you created, and it clearly states that this use case is not supported yet. Specifically because AMD does not ship NPUs on their server level CPUs yet. I'll just link to the second...

Hi, that depends on how you want to use it. From what I can tell the storage can either be exposed via NFS or CIFS, in which case we would discourage using it. The main datastore should use fast NVMe-based storage to facilitate swift and stable backups. However, you could also use it as a...

Hey, neben der aktiven Unterstützung des Projekts bieten Subscriptions (keine Lizenzen) hauptsächlich die folgenden zwei Vorteile: Zugang zum Proxmox Enterprise Repo Support durch unser Enterprise Supportteam ab einem Subscription Level von „Basic“ Ohne eine Subscription können immer noch...

You should really try to recover your RAID array in this case. What are you using to create the array?

Alright, but be aware that this is quite risky. I'm assuming you mean the boot drive of the VM in question. Can you provide the ID of the VM you want to recover? Your first post shows that you have disks for VMs 100 through 106. All these LVs are inactive, though. You could try to activate them...

How did you set up the raid array? How did you recover it after one disk failed? Can you also post the output of lsblk?