Search results

This is greate, thanks for provide PBS. I just update to version 0.9.7 both server and client, and I notice one issue: When ProxMox backup job failed in client side, the server side PBS datastore still keep running status. This issue also exist in version 0.9.1 PBS server and client.

Hi, I encuonter this issue too. I my case, I have to add "vga=normal" into boot menual kernel line, otherwise the installation will fail to initilize. And I found I can only initilize the installation when BIOS using Legacy model, If BIOS using UEFI model, installation also fail to initilize...

Hi, tom, thank you very much, I found the direct download link in the post you mentioned: http://download.proxmox.com/iso/

This is really sad news, as lots of server current still do not use any GPU, more than 90% of our servers just support VGA, now we can not install new version PVE directly.

Hi, since from PVE6.1, our Proxmox installation all failed in many type servers, we have to install PVE6.0 and then upgrade to new version. And today I just tried PVE6.2, and also failed, the last line messages is same: "\nInstallation aborted - unable to continue (type exit or CTRL-D to reboot)".

hi, i need to use wget command to download Proxmox ISO file, can anybody tell me the direct download URL of proxmox iso ? Thanks.

Hi fabian, thanks for notice. Yes, it is, guest VM got high load average after running backup, and unable to control even I stop the backup (can not shutdown or poweroff, need to kill KVM process in Host). I am looking how to update the qemu-guest-agent package for my CentOS 7(CloudLinux).

Hi every one, I just installed new 6.1 PVE and found snapshot backup is not working at all. I found the backup log ceased after the following line: INFO: issuing guest-agent 'fs-freeze' command I guess maybe qemu-guest-agent cause this issue, so I login into VM(CentOS7) and stop...

Thanks, when changed networking, PVE notice need to reboot hostnode, however networking lost after reboot, I need to go to hardware console to restart network. This issue is not the first time happening.

Hi, I encounter the same issue, host network interface lost settings after add another linux bridge, seems proxmox is using incorrect debian network interface options when modifing the /etc/network/interfaces files. Debain system seems only accept "_" but proxmox is using "-", for exampel...

hi, thanks for the information. I follow the steps to update cloud-init RPM package to epel-release's 18.3, every things are working well expect change root password. After checking cloud-init.log, I found CentOS6 always locked root password(by inserting "!!" into the /etc/shadow) when first...

Just found Proxmox change code Cloudinit.pm and cause Cloudbase-Init failed to set IP address: Cloudbase-Init error messages: C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log\cloudbase-init.log plugin 'NetworkConfigPlugin' failed with error '('Cannot set static IP address on network...

@encore, thanks for the correction, I had updated now. Btw, I found the way to eject/umount CDROM when Cloudbase-Init completed, please refer here if you are intrested: https://ask.cloudbase.it/question/2939/how-to-umount-cd-drive-after-cloudbase-init-completed/

@Craig St George Hi, thanks. In my case, the DNS is not important, i can setup in the windows template directly, however changing password of Administrator is my main goal, that also mens I need to set first_logon_behaviour=no. Disable the generate_random_password is very very important for...

Thanks. I finally succeed to setup IP/Hostname/Password with Windows2016/CoudbaseInit through Proxmox/CloudInit. I have to modify the CoudbaseInit python code and Proxmox/CloudInit perl code. Here are the changing I had done: (1) Change roxmox/CloudInit perl code to support configdrive2...

Hi, Thanks for your tips. I changed Cloudinit.pm, but only succeed to change IP address, can not change DNS/Hostname, and seems password always change with random one, so after reboot windows will always not able to login again.

Just encounter this error today, not way to stop VM in UI. And command line also failed: # qm stop 102 trying to acquire lock... can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout