Search results

Just backup then restore it to Proxmox.

I really don't understand how LXC works. I have only 10 LXC, CPU usage 20%, but 1 of my LXC has cpu usage 100% and caused Server Load 400! How to prevent this one LXC overloaded whole server? This overloaded LXC has Cores = 1, CPU Limit = 0, CPU Units = 1000

This new behavior is called thin-provisioning. You can see detail LVM using: # lvdisplay

Just testing on Centos 7 KVM, the mouse pointer very slow compare to Promox 4. Even text typing also slow. @tom : I suggest "noVNC setting button" displayed in the next version.

Just reinstall same server using Proxmox 4.4-24, now Console to Win7 VM 3-5 times faster!

Just remove the double routing. BTW, eth0 is not default naming since Proxmox 5.2, its using new format like "enp3s0" as shown in your debian config.

Just add your Secondary Public IP to VM and set to vmbr0. No need other bridge because Proxmox works as same as a Switch.

You don't need to create vmbr2. Delete this part: auto vmbr2 iface vmbr2 inet static address 54.39.49.187 netmask 255.255.255.255 bridge_ports none bridge_stp off bridge_fd 0 up ip route add 198.27.122.255/32 dev vmbr2 down ip route del 198.27.122.255/32 dev vmbr2 Just inside your VM: - enter...

Why Console slower 3-5 times to access Win7 compare to Proxmox 5.1? How to make it faster again?

As the error said you need to do "modprobe fuse", if there is no one then install fuse first.

Right, you need to have 2 vmbr: vmbr0 = for guest with Public IP vmbr1 = for guset with Private IP Just edit your /etc/network/interfaces to add new vmbr1. auto vmbr1 iface vmbr1 inet static address 192.168.0.1 netmask 255.255.255.0 bridge_ports none...

Which NAT of Web UI do you refer? Better upload a screen shoot. But usually I do NAT using this: # nano /etc/network/interfaces Then restart the networking via cmd line.

By default if you use vmbr0 then all guest can have dedicated IP public. For "Allow local network and internet via nat" which local network do you mean? The node or guest?

Fixed. Just change eth name back to old style: eth0, eth1, etc. nano /etc/default/grub GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0" update-grub Then ... revised /etc/network/interfaces to eth0.

I just try Proxmox 5.2-2 but unfortunately Iptables NAT does not work like Proxmox 5.1 does. # vmbr0: Bridging. Make sure to use only MAC adresses that were assigned to you. auto vmbr0 iface vmbr0 inet static address 10.10.10.1/24 gateway 10.10.10.254 bridge_ports...

Sorry ... it is a VM.

I try to restore a 6GB backup to "local-data" disk with new 1000GB size, but look like PCT does not accept vma format: # pct restore 239130 /mnt/backup1/dump/vzdump-qemu-239130-2018_05_19-18_24_35.vma.lzo --rootfs local-data:1000 Formatting '/mnt/data/images/239130/vm-239130-disk-1.raw'...

As you can see the Error say: "The network autoconfiguration was SUCCESSFUL. However, no DEFAULT ROUTE was set". You must follow set the gateway manually as I described before. Also no NAT required.

Do not use Auto Config for eth on Debian guest because the gateway not in the same network. Your subnet should be 255.255.255.255 instead 255.255.255.248

I see my Proxmox 5 show different CPU Usage for each LXC. Look at the Data Center - node name - then click Search menu.