Search results

In case someone in the future can benefit from our experience, here is a quick tutorial for loading a Barracuda (kvm) VM in Proxmox: Creating Barracuda VM on Proxmox Virtual Environment How to convert Barracuda KVM image to Proxmox LVM (raw) image Proxmox VE is a highly evolved virtual...

Getting very confused reading through so many OVS explanations and examples, most with complexities i don't need and none of which clearly answer my questions. Question 1 I have eth0 NIC connected to a line giving me a native VLAN (10.1.1.0/24) and a tagged (tag=2) VLAN (172.17.0.0/16). No...

I have a development proxmox box (non-susbscription) on which i ran apt-get udate && apt-get dist-upgrade. However after the reboot the gui is still 4.2 and not all packages upgraded. I did have some issues with this box in the past since this is the one we use to play with and break. Should...

Upgraded to VE 4.4 with subscription. System was working fine before. Now openvswitch is failing. 1. vmbr0 is popping in and out of "promiscuous mode" (as seen in /var/log/syslog) causing intermittent connection to console and web gui. I can only get to it now from server's KVM. Reply from...

I would like to contribute some additional information to https://pve.proxmox.com/wiki/Moving_disk_image_from_one_KVM_machine_to_another. How do i do this? 5. Now, using Proxmox Web Admin, we can delete the disks from the "old" VM-108 so they will be "unused". 6. To do a hot addition of the...

Hi, We currently have a single Proxmox 2.3-13 server (IBM 3650-M3) running 16 VM's. It is deployed with a 150Gb RAID1 system disk and a 2.3Tb RAID5 VM-Image disk, both LVM2. We have purchased a 2nd identical IBM 3650-M3 and we would like to configure a Proxmox 3.0 Cluster (not HA, just...

I noticed a couple of times now that restoring a vm in 2.3 takes a very long time, much longer than previous version. Restore time for a Win2003 with 2 HD's (32Gb & 50Gb) took 12 hours. Has anyone else experienced this? I AM glad for the new backup/restore systems because now the restores...

Every time i try to restore a .tar.lzo backup from command line: root@proxmox2b:~# qmrestore /mnt/iSCSI_Backup/dump/TestWin7-64-2012_07_31.tar.lzo 121 -storage ImageLVM extracting archive '/mnt/iSCSI_Backup/dump/TestWin7-64-2012_07_31.tar.lzo' extracting 'qemu-server.conf' from archive...

This is a continuation of the thread on restoring backups of vm's with large multiple disks. I believe the cause of the "tar: write error" was due to the system root disk being smaller than the vm disks being restored (restored to the 2nd "image" disk - very large). Our server with Proxmox...