On one server, when accessing my vm using RealVNC vncviewer, the vm stops abruptely.
The vm is a Windows 2008 R2 server.
Another vm on the same server has the same bug.
kvm[14289]: segfault at 7fffced77688 ip 000000000041b264 sp 00007fffce552100 error 6 in kvm[400000+28a000]
Any fix for this ?
Any component i can upgrade ?
# pveversion -v
pve-manager: 1.7-10 (pve-manager/1.7/5323)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.7-9
pve-kernel-2.6.32-3-pve: 2.6.32-18
pve-kernel-2.6.32-4-pve: 2.6.32-30
pve-kernel-2.6.35-1-pve: 2.6.35-9
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-1dso1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4
# cat /etc/qemu-server/205.conf
name: ddosql200
ide2: local:iso/xxxx,media=cdrom
bootdisk: virtio0
ostype: w2k8
memory: 5120
onboot: 1
sockets: 1
vlan10: virtio=xx:xx:xx:xx:xx:xx
cores: 3
virtio0: local:205/vm-205-disk-1.qcow2
boot: cd
freeze: 0
cpuunits: 1000
acpi: 1
kvm: 1
The vm is a Windows 2008 R2 server.
Another vm on the same server has the same bug.
kvm[14289]: segfault at 7fffced77688 ip 000000000041b264 sp 00007fffce552100 error 6 in kvm[400000+28a000]
Any fix for this ?
Any component i can upgrade ?
# pveversion -v
pve-manager: 1.7-10 (pve-manager/1.7/5323)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.7-9
pve-kernel-2.6.32-3-pve: 2.6.32-18
pve-kernel-2.6.32-4-pve: 2.6.32-30
pve-kernel-2.6.35-1-pve: 2.6.35-9
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-1dso1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4
# cat /etc/qemu-server/205.conf
name: ddosql200
ide2: local:iso/xxxx,media=cdrom
bootdisk: virtio0
ostype: w2k8
memory: 5120
onboot: 1
sockets: 1
vlan10: virtio=xx:xx:xx:xx:xx:xx
cores: 3
virtio0: local:205/vm-205-disk-1.qcow2
boot: cd
freeze: 0
cpuunits: 1000
acpi: 1
kvm: 1