Search results

I've been studying high IO delay at one of my servers and found that barriers could increase IO delay. If barrier is turned on (/proc/mounts) it could be a reason of high IO delay.

All drivers are installed (Intel and virtio). But it doesn't work with all types of network cards. Even realtec network card doesn't work.

Nope, a fixed IP address didn't help either. Looks like there is no network connection between VM and host.

When I had an unusual high IO delay (even when all VMs were turned off) I just rebooted my server. That helped me.

The network card is not disconnected. I even tried to add new virtio and IntelE1000 network cards but it didn't help me. All other VMs work fine. I have 18 VMs on the same server and all of them work fine.

One of my VMs (Windows XP) has lost connection and I can't recovery it anymore. All the others VMs work fine on the same node. Network: IntelE1000 in NAT Mode. WindowsXP guest shows there are no IP address allocated to the network card. Looks like Proxmox doesn't allocate an IP address for this...

Where can I change this limit? I can only see KVM Hardware Acceleration for each VM via web interface.

Trying to re-install a fresh PVE 3.4-11... Yep, the KVM Hardware Virtualization is enabled. The max number of 7 instances doesn't look realistic for me. CPU is a shared resource. Xeon E3-1246 has the same max number of thread as i7, but works nice at 20+ VMs.

Well, the CPU Proxmox requirements are: CPU: 64bit (Intel EMT64 or AMD64) Intel VT/AMD-V I think any i7 CPU would be fine.

I used Soft Raid level 1 and lvm. Something like this: PART /boot ext3 512M PART lvm vg0 all LV vg0 root / ext4 20G LV vg0 swap swap swap 16G

The hoster says they don't have a BIOS update yet. i7-6700 was released 4 month ago.

The CPU is Default (kvm64) and Windows XP is 32-bit. I have a couple of servers with Xeon CPU E3-1246 v3 and PVE version: 3.4-11. They work fine, but a new one with i7-6700 doesn't work correctly. Also I noticed ACPI Errors and "CPU stuck for..." And it crashes now when I'm trying to clone a...

7 WinXP VMs were working fine, but when I added 8th it begun crashing. I have 20 WinXP VMs on PVE version: 3.4-11 and they work nice. But my new server doesn't work.

At first I installed ProxMox 3.4-11 on my new server (i7-6700, 32GB Ram) at Hetzner. It worked nice for several days. When I started to add and launch new VMs (Windows XP) it begun crashing: Previous pveversion: # pveversion -v proxmox-ve-2.6.32: 3.4-166 (running kernel: 2.6.32-43-pve)...