Search results

hostname -f shows pve1.example.com. So to what extent should I be worried?

Hello, I would like to change the FQDN in a cluster which we mainly use to access the administrative interface. I see that in /etc/hosts both the fqdn and the one-label names are set: 127.0.0.1 localhost.localdomain localhost 10.88.88.231 pve1.example.com pve1 10.88.88.232 pve2.example.com...

@jdancer Would you mind sharing what do you go by when setting the minimum and maximum limits for the RAM with ballooning turned on?

I often had issues with the VMs not seeing all the available memory and that would lead to OOM. Also, if the minimum limit is too low, the VM might not even boot and get into kernel panic directly, as the virtual machine might see only that minium available memory, which I actually don't...

Hello, I think it would be really great if renaming firewall aliases would dynamically update the firewall rules and the security groups instead of breaking them. At the moment, renaming aliases does not update the rules/security groups which leads to them pointing to a non-existent (previous)...

I'm not sure why the fact that you can see all the disks (including the S/N) is played down like that. Does this occur with standard LXC container outside Proxmox? I know it doesn't happen with docker in any case (not that I believe docker is better) and most probably not in podman either.

I wonder how this is not a huge security concern. Why does Proxmox allow for such privileges inside a container?

Never mind, I was able to solve it with the help of this link https://bobcares.com/blog/change-hostname-proxmox/ I also had to change the "nodes" directive for /etc/pve/storage.conf to the name of the new node.

Ich bin der Anleitung da gefolgt (https://bobcares.com/blog/change-hostname-proxmox/) und es hat geklappt, ich habe alles Dateien aus dem alten Node-Ordner zu dem Neuen umgezogen, dann habe ich den Hostname geändert und /etc/hosts angepasst und das war's. Es gibt nur ein kleines Problem, da er...

I have several virtual machines on a node that I'm trying to rename, but when I try to copy the configuration files, I get the error that the file already exists: root@teilnahmslos:/etc/pve/nodes/pve1/qemu-server# cp 100.conf /etc/pve/nodes/teilnahmslos/qemu-server/ cp: cannot create regular...

Hallo, Ich habe den Hostname von meinem one-node Cluster von „pve1“ zu „teilnahmslos“ geändert. cat /etc/hostname teilnahmslos cat /etc/hosts 127.0.0.1 localhost.localdomain localhost 192.168.111.20 teilnahmslos Ich habe dann alle Proxmox Dienste umsonst neu gestartet (durch systemctl) und...

Any updates regarding this? It would make managing the firewall so much easier.

Don't you maybe mean to say in the "Options" section under "Firewall" after selecting the virtual machine? I don't see anything in the hardware section related to this. I'm encountering the same issue and I've no idea what's going on. I've activated the firewall for all virtual machines, but it...

Switching to telmate/proxmox 2.9.11 works in that the error is ignored and the provisioning works. Indeed, as far as I can understand, terraform tries to attach the cloud drive to scsi0, and it fails to do so because it says that it's already attached to ide0. And I've no idea where this is...

I'm provisioning a virtual machine from a packer clone using terraform. My question is not related to terraform, this is just the context, but I eventually end up getting this error: ``` update VM 108: -agent 1 -bios seabios -boot c -bootdisk scsi0 -cicustom...

I have to say this is one of the more important reasons why we have to use vsphere instead of proxmox in production. I would have liked to understand the thinking behind it/the general direction. There are a lot of good things about proxmox (like the clearly superior GUI to that of vSphere) and...

Well, I can assure you that in the meantime I've almost forgotten what LXC-containers mean :D

@brucexx I'm not sure anymore if what they say in the link is correct though. I also had a look at the actual CPU instruction sets and there were around 2 more flags for kvm64 than for qemu64. So we need more context. So I wouldn't suggest anyone switching to qemu64 at this point :) Here are the...

I've come across this link https://qemu.readthedocs.io/en/latest/system/qemu-cpu-models.html#default-x86-cpu-models where it's stated that using kvm is not recommended and that you should use qemu instead, because it exposes more many featuresets. About kvm under Other non-recommended x86 CPUs...

Any intention of adding this feature? Using terraform/packer with proxmox becomes really difficult because of this limitation.