Search results

which version you are running? define a shared storage for backups, create a backup task for that vm - or do a manual backup with 'Backup now' option on the 'Backup' tab of the vm; Storage could also be a local directory you add on the Storage tab; On the second server also configure the same...

do you see the nic in the output of 'lspci'

Re: Looking for a Proxmox mentor to assist small organization to upgrade a Proxmox in mircosoft has a procedure for that, either you can do it online or simply call them to get the new key - it's normally done in few minutes

boot into the correct kernel and it should work; see the wiki for installation instructions - this is what you missed: apt-get remove linux-image-amd64 linux-image-3.2.0-4-amd64 update-grub

you can edit the group lines on startup by pressing 'e' or boot via live cd

possibly your drive order have changed - you might check /etc/fstab and /boot/grub/grub.cfg and switch to UUID's /cat/proc/partitions ls -l /dev/disk/by-uuid/

Not sure what you mean with 'GENERAL' but i guess it's based to your switch model and software; If you have on the switch VLAN101 defined and added to the interfaces you need to create the VLAN interfaces on the server and workstation; # vlan for Server auto eth0.101 iface eth0.101 inet...

looks like your switch only have an ip address in vlan 1 and not in vlan 101

There is no converting of the disk images, with virtio you just change the way how your disk images are accessed; Virtio gives you more performance than ide and therefore a good choice or necessary on some installations; And you can easily switch back from virtio to ide if you don't need or...

try using proto=udp instead tcp and hard,intr instead soft and see if that changes the behavior

it's hard to say something without details about your network environment but i would do tcpdumps on your switch/host/vm interfaces to find out from which direction they are coming in... i had a similar case where a customer had a layer-2 connection between two sites where the connection were...

can you post a qemu config file of such an vm? and also a screenshot of the device manager (uncollapsed) i moved a w2k3 vm from PVE 1.9 to 3.1 without any issues two weeks ago; you could try also moving to virtio where i do it that way: add a new harddisk with virtio shutdown/start the vm that...

is the nfs storage marked as 'shared' ?

there is a option -bwlimit for vzdump you can set in vzdump.conf for limiting io on backups, but not sure if this takes also effect on restores;

how many entries do you have in your arp cache? have you checked the network settings on your host an vm's? maybe your broadcast domain is to large

try 'qemu-img info vmxxx-disk-1.qcow2' on your existing file, then create a vm with a disk of the same size and replace it with your existing file; the nic you will possibly see the installed driver inside your vm, cpu might be default and the other parameters like memory... you maybe remember...

i assume both nic's are connected to a switch (preferably not the same) i would do that: auto lo iface lo inet loopback iface eth0 inet manual iface eth1 inet manual auto bond0 iface bond0 inet manual bond_mode active-backup bond_miimon 100 bond_updelay 200 bond_downdelay 200...

to be more specific: /etc/hosts may contain hostnames with and without dots where you need to differentiate between FQDN, domain and host part; /etc/hostname can only contain the host part without the domain part;

there was a way to do that on 2.x, but not sure if this works on the latest version too: http://undefinederror.org/how-to-reset-cluster-configuration-in-proxmox-2/

You are referring to 'hostname' in the man pages which is a FQDN that contains dots but the 'host part' of a FQDN is only the name before the first dot; see the RFC's for DNS;