Hello, All!
There is one important issue.
As a guest OS installed Windows Server 2012R2.
As a model of network card is selected: VirtIO.
On the Windows is installed drivers virtio-win-0.1.105
Problem: Guest OS Windows 2012R2 at any time may hold.
We see that the processor is loaded at 100% network traffic is stopped, the read/write from the hard drive is not performed
The only way to hard reset only via "qm reset" or "qm stop".
This occurs only if a network card is selected: VirtIO.
However, the use model Intel E1000 or RTL8139 just not possible for the Windows 2012R2 installed VoIP server and it makes problems with the quality of communication.
versions:
Config here:
Windows virtio driver: virtio-win-0.1.105 (The same problem was with the previous versions of the driver)
There is one important issue.
As a guest OS installed Windows Server 2012R2.
As a model of network card is selected: VirtIO.
On the Windows is installed drivers virtio-win-0.1.105
Problem: Guest OS Windows 2012R2 at any time may hold.
We see that the processor is loaded at 100% network traffic is stopped, the read/write from the hard drive is not performed
The only way to hard reset only via "qm reset" or "qm stop".
This occurs only if a network card is selected: VirtIO.
However, the use model Intel E1000 or RTL8139 just not possible for the Windows 2012R2 installed VoIP server and it makes problems with the quality of communication.
versions:
Code:
pveversion -v
proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-39-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-39-pve: 2.6.32-156
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-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.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1Config here:
Code:
bootdisk: virtio0
cores: 4
cpu: host
memory: 6144
name: SIP-SERVER
net0: virtio=8E:DC:97:A1:F6:4A,bridge=vmbr1
numa: 0
ostype: win8
sockets: 1
usb0: host=2-1.2
virtio0: local:701/vm-701-disk-1.qcow2,format=qcow2,size=64G
virtio1: local:701/vm-701-disk-2.qcow2,format=qcow2,size=64G
virtio2: local:701/vm-701-disk-3.qcow2,format=qcow2,size=128GWindows virtio driver: virtio-win-0.1.105 (The same problem was with the previous versions of the driver)