Hi,
We are still seeing backup issues with Proxmox. Issues only occour on Windows VMs.
Backup completes 100%, no errors. But inside Windows VM we receive an Atapi event ID 9 (The device, \Device\Ide\IdePort0, did not respond within the timeout period.).
And Windows either get unrespondable or Windows will keep running but database will crash.
It's a Windows 2003 R2 server. Doesn't use Virtio drivers. Any clues?
Here are my VM config:
root@proxmox:~# cat /etc/pve/local/qemu-server/101.conf
bootdisk: ide0
cores: 1
cpu: kvm64
ide0: local:101/vm-101-disk-1.raw,format=raw,size=15G
ide2: cdrom,media=cdrom
memory: 512
name: w2003-dev
net0: e1000=6A:E5:5A:CC:E6:ED,bridge=vmbr0
ostype: wxp
sockets: 1
vga: std
And my pveversion:
root@proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
We are still seeing backup issues with Proxmox. Issues only occour on Windows VMs.
Backup completes 100%, no errors. But inside Windows VM we receive an Atapi event ID 9 (The device, \Device\Ide\IdePort0, did not respond within the timeout period.).
And Windows either get unrespondable or Windows will keep running but database will crash.
It's a Windows 2003 R2 server. Doesn't use Virtio drivers. Any clues?
Here are my VM config:
root@proxmox:~# cat /etc/pve/local/qemu-server/101.conf
bootdisk: ide0
cores: 1
cpu: kvm64
ide0: local:101/vm-101-disk-1.raw,format=raw,size=15G
ide2: cdrom,media=cdrom
memory: 512
name: w2003-dev
net0: e1000=6A:E5:5A:CC:E6:ED,bridge=vmbr0
ostype: wxp
sockets: 1
vga: std
And my pveversion:
root@proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1