I have been using PVE for some time and have been really happy with it. I have recently migrated my Win2K3 server at work to a KVM VM running under PVE, as part of this I decided to start taking advantage of the snapshot setup in PVE (which I haven't used previously).
I have 2 HDDs (sda & sdb). I did a default PVE v1.7 install to a 1TB WD 'Black' drive (sda) and I have just added a 1TB WD 'Blue' drive (sdb) specifically for storage of backups. I have formatted sdb as a single ext3 partition (sdb1) and mounted it to /srv/hdd2 (in fstab). Then using the WebUI I added /srv/hdd2 as a backup target drive and set backups to run. I have a few OVZ guests and they backup fine, as does another KVM guest (WinXP) but when I backup my Win2K3 guest all communication with the PVE host stops after 40 mins. I have tried a few different things, thinking that I must've done something wrong but I'm fast running out of ideas. Initially I thought it was something to do with networking but it appears to be a kernel panic (see below).
The 2K3 guest has 2 separate .raw hdd images (which I created from the 2 partitions on the physical server) running beautifully with virtio drivers (better performance than what I was getting on hardware!). Everything runs sweet until I run a backup, although the first drive seems to complete it's backup. I do not have a screen or keyboard connected to the host, but after a couple of attempts (and a bit of research) I tried running the backup manually (from a SSH session) like this:
it froze again (as I expected). In the terminal all seemed normal but I got this at the end (and no email to the designated address):
The only USB device is a UPS so I assume that's what it's complaining about for some reason. I had previously tried it with the UPS disconnected and had the same problem (although I ran it from the WebUI so haven't any additional output from that).
Some extra info:
After running 2 (unsuccessful) backups this morning:
Also BTW I tried aptitude dist-upgrade but there is a dependency issue (buggy Debian package by the look?) apparently so I have only done an upgrade.
I have 2 HDDs (sda & sdb). I did a default PVE v1.7 install to a 1TB WD 'Black' drive (sda) and I have just added a 1TB WD 'Blue' drive (sdb) specifically for storage of backups. I have formatted sdb as a single ext3 partition (sdb1) and mounted it to /srv/hdd2 (in fstab). Then using the WebUI I added /srv/hdd2 as a backup target drive and set backups to run. I have a few OVZ guests and they backup fine, as does another KVM guest (WinXP) but when I backup my Win2K3 guest all communication with the PVE host stops after 40 mins. I have tried a few different things, thinking that I must've done something wrong but I'm fast running out of ideas. Initially I thought it was something to do with networking but it appears to be a kernel panic (see below).
The 2K3 guest has 2 separate .raw hdd images (which I created from the 2 partitions on the physical server) running beautifully with virtio drivers (better performance than what I was getting on hardware!). Everything runs sweet until I run a backup, although the first drive seems to complete it's backup. I do not have a screen or keyboard connected to the host, but after a couple of attempts (and a bit of research) I tried running the backup manually (from a SSH session) like this:
Code:
vzdump --snapshot --storage backup-hdd2 --mailto jeremy@domain.org.au 251
Code:
Message from syslogd@proxmox at Mar 19 10:39:29 ...
kernel:general protection fault: 0000 [#1] SMP
Message from syslogd@proxmox at Mar 19 10:39:29 ...
kernel:last sysfs file: /sys/devices/pci0000:00/0000:00:16.0/usb7/idVendor
Message from syslogd@proxmox at Mar 19 10:39:29 ...
kernel:Stack:
Message from syslogd@proxmox at Mar 19 10:39:29 ...
kernel:Call Trace:
Message from syslogd@proxmox at Mar 19 10:39:29 ...
kernel:Code: 60 eb 08 c7 44 24 6c 00 00 00 00 e8 00 4f 22 e1 48 8b 7c 24 20 e8 f2 60 22 e1 e9 0f 02 00 00 49 8b 1f 48 8d 73 60 48 89 74 24 58 <f0> ff 43 60 31 ed f6 03 02 74 68 f0 0f ba 2b 02 19 c0 85 c0 bdSome extra info:
After running 2 (unsuccessful) backups this morning:
Code:
proxmox:/srv/hdd2# du -sh *
16K lost+found
33G vzdump-qemu-251-2011_03_19-07_00_02.dat
8.0K vzdump-qemu-251-2011_03_19-07_00_02.tmp
21G vzdump-qemu-251-2011_03_19-09_54_30.dat
8.0K vzdump-qemu-251-2011_03_19-09_54_30.tmp
Code:
proxmox:~# pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.7-30
pve-kernel-2.6.32-4-pve: 2.6.32-30
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4