Search results

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.

After fdisk /dev/sdb then you must create a file system there: # mkfs.ext4 /dev/sdb1 Now mounting it: # mount /dev/sdb1 /media/RAID10/ Go to Proxmox VE Web to add your new Strorage

What kind of storage did you use in the Cluster before?

Thanks for clarification.

#pvecm delnode node-x Will remove node-x from cluster w/o downtime to any VPSes.

I think this is Proxmox VE 5 bug. On version 4, KSM automatically active and start sharing when reach 80% of RAM. # systemctl status ksmtuned Unit ksmtuned.service could not be found. # # apt-get install ksm* Reading package lists... Done Building dependency tree Reading state information...

This will show your previous PV: #pvscan

Inside VM check if service on port 8080 is running. $ sudo netstat -ntlp | grep :8080

What was displayed on Console? Have you try to set "cache=none"?

Try to use another IP or change Virtual MAC (delete then add again Virtual MAC).

@Cantalupo: please open new thread and don't forget to show your "/etc/pve/lxc/ID.conf" (where ID is your container's ID)

If the CT imported from OpenVZ then you must set the network configuration manually to make LXC works. You must: Add MAC Address which OpenVZ doesn't require it CIDR for IP. In OpenVZ you write 192.168.1.1 but LXC must be 192.168.1.1/24 for example Add Gateway which OpenVZ doesn't require it

This is the solution. Remove any existing partition on your HDD. But I prefer ext4 because faster, except you need ZFS RAID.

Yes possible. Just copy the image to local disks then use API to create, suspend or destroy any VM. VM with same ID is not possible in SAME NODE, so never created./executed too. If a node die then all VMs inside death node will die too. The fastest and save approach is copy your GOLDEN image...