Search results

Today i had occasion to try to restore a vm backup as another VMID for use as a "test" vm while my production vm's were running as normal. I used the GUI to do this. A few minutes into the process the previous problem documented in this thread reoccurred. First the GUI display of vm's went...

I am having the same difficulty on the GUI with my node becoming red and all vm's showing down while everything is actually running. HOWEVER, i am NOT running a HA or cluster. Just a single node. It seems to occur most often after my weekend backup. But this morning (mid-week - no backup...

Oh right, thank you. It was a late night... %-/

Thank you Dietmar. It is now updated. pveversion -v pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46) running kernel: 2.6.32-12-pve proxmox-ve-2.6.32: 2.1-74 pve-kernel-2.6.32-11-pve: 2.6.32-66 pve-kernel-2.6.32-14-pve: 2.6.32-74 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.3-1...

root@proxmox2b:~# pveversion -v pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a) running kernel: 2.6.32-12-pve proxmox-ve-2.6.32: 2.1-68 pve-kernel-2.6.32-11-pve: 2.6.32-66 pve-kernel-2.6.32-12-pve: 2.6.32-68 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.3-1 openais-pve: 1.1.4-2 libqb...

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...

Your loop most likely is caused by an incompatible driver. If you're concerned about removing it then you should back up your hard drive with clonezilla or similar so you can restore it after you're done.

Anyone?

I've encountered this issue with several different physical machines that i virtualized with SelfImage to Proxmox (btw, these instances would not boot into safe mode either.) The culprits were these: - Video driver. - Fiber channel driver and the system expecting to see a drive via fc. - Backup...

000

moved to: Upgrading Root disk on Dual Disk System

have you looked at this? http://support.microsoft.com/kb/958752

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...

There may be a driver (or sometimes some software) loaded on the physical machine that must be uninstalled before the SelfImage. I have experienced this same issue. In all but one case, removing all hardware specific drivers solved the issue (the one exception was a Windows Domain Controller.)

Tried again to restore the same vm from a fresh backup to a new vm. I noticed the entire system starting to stutter (literally see pictures). The first picture was a 30-40 minutes into the restore. Then about 10 minutes later the stuttering got worse, connecting to vm consoles was...

I have NOT tried tar_1.26-4_amd64.deb. However i tried to do a fresh Backup and then Restore to an new vm (131) within the 2.1 gui: extracting archive '/mnt/iSCSI_Backup/dump/vzdump-qemu-115-2012_06_20-16_17_16.tar.lzo' extracting 'qemu-server.conf' from archive extracting...

virtio0 = '/dev/ImageDisk/vm-115-disk-1' [66.00 GiB] inherit virtio1 = '/dev/ImageDisk/vm-115-disk-2' [126.00 GiB] inherit

Is this what you are asking for?: root@proxmox2a:~# cat /etc/pve/qemu-server/115.conf bootdisk: virtio0 cores: 4 ide2: local:iso/ProxmoxWindowsUtilities.iso,media=cdrom memory: 4096 name: TSBUSQL3 net0: virtio=5A:B0:5A:02:34:88,bridge=vmbr5 net1: virtio=EE:AA:6A:40:91:67,bridge=vmbr0...

Yes. Every time.

I am running into the exact same issue. I believe the problem occurs when there is a disk in the archive that is larger than the root partition. I think that the tar script in the restore procedure uses the root partition as its extraction area. Purely speculative. I have not been able to...