Search results

We have a issue where LVM's continue to fail so we want to move from LVM based to File based on shared storage. Has anyone done this successfully without having to reboot the VM?

After a reboot of Proxmox, about 1/3 to 1/2 the VM's are down and say: No bootable disk for the VM. All VM's are on a LVM and the LVM is up and usable. Any ideas?

We don't use the firewall, however during the upgrade it apparently masked. As son as I uninstalled pve-firewall, unmasked and then ran the upgrade again it worked fine.

My fix was unmasking the pve.firewall service, it then installed and configured everything properly Note: This is not part of the instructions.

/etc/hosts file is correct, dpkg --configure -a has been ran and I still get errors Any help would be appreciated: root@proxmox2:~# apt-get install proxmox-ve Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be...

Anyone know how the GUI and API boots or restarts a VM? We need to restart the snmpd service after a VM is booted or restarted so that our bandwidth logging works correctly so hoping I can just add a service snmpd restart to wherever the GUI and API restarts the vm

Thanks dietmar, missed the DELETE tab. Feel like an idiot but the module works and is onto the next phase now:)

@spirit - I do NOT work for WHMCS. Im working on a WHMCS Module for internal use and at some point we may release it GPL or for sale but for now its internal use only. The API has create, start, stop and management features but does not have a Destroy/Remove/Terminate a full VM like the gui...

According to http://pve.proxmox.com/pve2-api-doc/ there is no Destroy/Remove command for a QEMU. Any chance of getting that added to the API? If so, then I can have a complete proxmox module for WHMCS thats fully automated

I understand its different but instead of spending hours rewriting our module, it'd be nice to be able to create a directory called api in /usr/share/pve-manager/root just like we did on 1.9 and put our API stuff in there and have it accessible from https://ip:8006/api/blah.php without having to...

If I created a directory in /usr/share/pve-manager/root how would I allow access to it and any files in it without being lgoged in to the pve-manager? I am attempting to migrate our API for WHMCS we wrote from 1.9 to 2.x and the API is moved but i cant access it due to permissions Im assuming

Honestly 1.9 is better than 2.x to us with the GUI and the API we have wrote.

Havent touched the PVE for months but now need to create a new VM and when we attempt to create we get the following: Internal Server ErrorThe server encountered an internal error or misconfiguration and was unable to complete your request.Please contact the server administrator, root and...

Until they bring out the API we wrote our own API that will work for v1 (tested) or v2 most likely (untested) that interfaces with our module that does the start/stop/suspend/unsuspend. Anything more than that hasn't been developed yet. Contact me off list if your interested

Start/Stop/Reboot and suspend/unsuspend

Still finish up testing. It has KVM built right now. If someone wants i'll build the openvz side. Right now it handles start/stop/restart only Contact me offline for testing details/suggestions email: jmeyers@webbytechnologies.com AIM: WebbyTech Skype: WebbyTech

We were looking fore something like this and we sat down and made a module in WHMCS for starting/stopping/rebooting/setting up openvz and kvm based VM's in ProxMox this weekend. It uses a quick and dirty API we also programmed that goes on the actual proxmox server

Sorry for bringing up a thread from the past but we were looking fore something like this and we sat down and made a module in WHMCS for starting/stopping/rebooting/setting up openvz and kvm based VM's in ProxMox this weekend. It uses a quick and dirty API we also programmed on each proxmox server