Search results

Hello Klas, Not really. Note that - in order to avoid loosing data by mistake - completely removing a disk needs two steps: 1. Select the disk and "Remove" => the disks remains in the storage, but will not be connected to VM, seen as "unused" in GUI 2. Select the "Unused Disk" and "Remove"...

No - but what would be the advantage of this?

Hello JustaGuy, Note that the delay timer runs after the VM has started and is the waiting time until the next VM starts. In case of order "any" the order is made by VM ID (but it´s recommended to define the order according to your needs). See also...

Hello iconvergence I suppose it will come when upgrading to Debian Jessie (vzctl 4.7) - current vzctl in Proxmoy is 4.0 - probably 1st half of 2015. Kind regards Mr.Holmes

Hello monty, Check settings of gateway and DNS in WEB GUI see example in attachment Kind regards Mr.Holmes

Hello yecine06, - your usb memory stick seems to be at 3-6 (you specified 2-1), and your 3G stick at 3-4 - after setting (in config file directly or via "qm set") you must shut down and start the VM (not just a reload!) - don't be confused by the expression "update", it refers to config file...

Hello LUNATECH You have to adjust it at your client, see http://setaoffice.com/2014/01/20/java-application-your-security-settings-have-blocked-a-self-signed-application-from-running/ But much better would be to use Proxmox VE 3.3 which supports noVNC (it´s the default there!) which does not...

Hello yecine06 Did you try it with another device (e.g. an usb memory stick) and/or with another VM? I prefer to use the qm command, works without any problems; it would be in your case qm set <vm-id> -usb0 host=3-4 or qm set <vm-id> -usb0 host=12d1:1446 kind regards Mr.Holmes

Hello ayankhan aptitude install pve-kernel-2.6.32-32-pve in order to get the newest 2.6.32 kernel. If you want to use a kernel which is still installed it is sufficient to remove kernel 3.10 from grub boot menu (important: this is not automatically done when you remove 3.10 kernel...

Hello Rafael Can you precise this with an example containing successful / unsuccessful ping etc and describe your network configuration (e.g. by posting /etc/network/interfaces from both host and VM? Kind regards Mr.Holmes

Hello webdev, Can you post - host´s /etc/network/interfaces - host´s /etc/pve/openvz/pve/<ct-id>.conf - failed and successful ping examples I rough idea (even I cannot imagine details) is that your provider´s switch checks MAC addresses and only after learning that the VM has an accepted...

Hello Mello21century, Did you 213.136.87.* get from your provider? And how are you connected with internet? - Behind a NAT router at 5.189.190.0/24? In that case also venet0:0 must have a 5.189.190.0/24n address .... But strange that we don´t see the NAT router in traceroute. - If directly...

Hello fragger Open vSwitch has to be installed from Proxmox repository (if used in Proxmox hosts, the standard Wheezy package does not work well in Proxmox!) deb http://download.proxmox.com/debian wheezy pve-no-subscription You have to use version 2.0.90-... verify if available by...

Hello dr-evil I posted already any: you answered but did not specify what in particular went wrong. You wrote and backup to local storage too? If "Yes" this workaround must work, or ....? Kind regards Mr.Holmes

Hello UserIsNew In principle ok but the first cp command has to be slightly different. Here is an example, I created container 1094 by copying it from 1093, in my case the storage is /mnt/pve/vpx and directory for configuration files /etc/pve/openvz: cp -a -v /mnt/pve/vpx/private/1093/...

What does it mean? What kind of problems you had (with vzdump or mv)?

Strange, difficult to say (without deeper investigation) - but the following workaround can help: #create the backup file in a local storage vzdump 100 -dumpdir /temp/ # move to your network storage mv /temp/*.vma /netstorage/dump/.

Hello Felix As far as I understood each container has its own public IP - so you don´t need a NAT; assign this IP to venet0 of the container (you can keep 10.0.0.112 too) and that´s it! The explaination for you error is probably is follows: ftp-protocol exchanges address and port values...

Hello dr-evil Nothing, I think - the problem is rather that your environment does not really support jumbo mtus. Probably it is not possible to accelerate the backup process by improving the network speed - the main effort is extracting data and compress them. I usually have (physical, that...

Hello bhagat Yes, I had. Solved the problem by adding in the NFS server in file /etc/exports "no_root_squash", e.g. like this /nfsshare 10.1.0.0/255.255.0.0(rw,async,no_root_squash) Success! Mr.Holmes