Search results

I have a server with several storages, different performance classes. Using the GUI how fo I change a container, or a VM, so it migrates all its files to a different partition? All inside the same server.

I have a container with 32 cores, and top show CPU consumption is always zero on the top panel, not in the per-process detail.

Proxmox uses Debian 9. I need to add a GUI to Debian, so I may use an app that requires a GUI. Can somebody provide a list of commands so I may do so safely?

BOOTPROTO=none is wrong if you are to have any IP address, the right options are static or dhcp. "none" means the interface is UP but is not communicating with the network, nor it is advertising its presence. In the Debian world there is no "none", but the equivalent is "manual". I use it all...

No, it does not. The issue is this: if you set a static IP address in the configuration, at booting, the container still has BOOTPROTO=none, when it should be BOOTPROTO=static. Since it has BOOTPROTO=none, it defaults to DHCP. If I set "static" in the configuration, it has to migrate to the...

I found that all containers have the same issue. Proxmox rewrites the network and always sets erroneously the BOOTPROTO=none when it should not rewrite anything. Also it messes up the file /etc/resolv.conf, deleting what we put in the line DNS1=XX.X.XX.XX, and adding nameserver=192.168.0.1...

I created a Fedora 27 container with a public IP address, but the resulting IP inside the container is DHCP. I am at a loss as how to fix this, since the configuration is correct. Is there an override to the automatic overwriting of network files?

Is it possible that you may somehow automate migrating of foreign LXC containers via a Bash script? The customer would supply only IP address and root password of existing host and the name of a stopped container.

Maybe I am misunderstanding the Proxmox LXC model. The free, regular LXC containers are invisible to Proxmox. Please correct me if I am wrong.

I brought in my existing LXC containers into Debian, and they work perfectly, I can manage them with the regular lxc command list. But Proxmox only shows its own containers, not all LXC containers. Proxmox containers must coexist and be managed along with regular LXC, directory-backed...

I have a container which needs two interfaces and certain features, like this auto lo eth0 eth1 iface lo inet loopback allow-hotplug eth0 eth1 iface eth0 inet static address 192.168.11.38 netmask 255.255.255.0 gateway 192.168.88.1 mtu 1458 post-up ip route...

That did not work at all with Windows 2016 Server. The only way was to reinstall from scratch using Virtio. The SCSI driver is not loadable by windows.

I converted a windows virtual machine to a template, but want to add more updates. Is there a way to convert it back to a regular VM? In Vmware that is permitted.

Yes I did. There is something missing in the windows installation that makes the disk unbootable except with IDE

The secret is to use virtio as boot device and to load the driver from the ISO, not after the fact.

Actually I added a virtio-block disk, as a second disk, and the driver worked. But then I changed the first drive to virtio, reattached it, and it does not boot. I need that he VM boots from virtio or SCSI.

One of my first tasks since we decided to move to Proxmox is to install a version of Windows 2016 Server. Unless you use a slow-performing IDE emulation, unsuited for databases, it is impossible. If I select the SCSI drive in Proxmox, the default, Windows cannot find a driver in the latest ISO...

This model of isolation, siloed, has a big flaw. Typically I move LXC containers from host to host using RSYNC. With the Proxmox implementation it is impossible. I have many containers with apps that are difficult or impossible to install, how do I move containers in and out of Proxmox. We need...

I am dismantling a Vmware ESX and a Hyper-V server, plus want to bring into Proxmox dozens of existing LXC containers that I may tar or RSYNC into the Proxmox server. Specially in the case of foreign LXC containers that reside on the file system of another host, is there a mechanism to migrate...

I need to copy files from the host and viceversa, like it is possible in LXC. "entering" alone is not sufficient, I need to mount the container´s space. Is there a way?