Search results

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.

The procedure to resize Proxmox local partition same as Debian way.

Then better "Proxmox VE 5.1 2nd ISO release" called as Proxmox VE 5.1-2 ISO release as written on the proxmox-ve_5.1-2.iso on the download section.

This makes confuse ... you should call it as 5.1.1 (or 5.2) . Now, the 5.1 documentation was wrong, also your press release wrong too. And all articles according to First Release of Proxmox 5.1 were wrong also :( Then your third 5.1 :( should be 5.1.2 (or 5.3) 1 more ... the Roadmap also wrong :(

According to your attachment, netmask for 255.255.255.0 in CIDR format is not /32, instead /24

Do you do apt-get upgrade before reboot? If not then why you reboot (maybe replace some adapter) ?

Check the script start_services.sh at line 4. You will see which file or folder need enough permission, usually give root 777 will solve this issue.

Just using Proxmox VE iso to install with its default partition. Put Promox VE on 2 x 320GB SSD in RAID 1. The 14 HDDs for VPS in RAID 10 mode. Other disks can be removed from Server to make it simple.