Search results

Woot, that fixed it, thanks.

Any ideas or updates on this issue?

ii pve-qemu-kvm 1.4-17 amd64 Full virtualization on x86 hardware abbca35bcaae484c7794af4f4bc28fd1 /usr/bin/kvm.old I was just testing.

copied kvm from my old server which is 2.3 and that let it start...

I had virt-manager qemu n all that installed before proxmox so I think thats causing the problem but am unsure why it still sees qemu-kvm after I've removed it I am also seeing this on my new install and not on my old, kvm --version kvm: /usr/lib/x86_64-linux-gnu/libspice-server.so.1: version...

root@tsunade:/var/lib/vz/template/iso# pveversion -v proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve) pve-manager: 3.1-4 (running version: 3.1-4/f6816604) pve-kernel-2.6.32-23-pve: 2.6.32-109 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.5-1 openais-pve: 1.1.4-3 libqb0...

When I start the VM that I restored onto 3.0 from 2.3 it ends up throwing an error, I can't seem to find any information on this anywhere. TASK ERROR: detected old qemu-kvm binary (unknown)

Virtio, running it with 4 cores and running wheezy. On windows I am using e1000

So I got my new dedicated server on a gigabit line setup, I got everything running fine, just that when I am testing my upstream bandwidth I get limited on the proxmox host and linux vms, but its fine on my windows vm, all vms are KVM. To better explain My Proxmox Host Bare Metal Server gets...

I have a dedicated server running proxmox 2.3, I have tested every type of setup possible on the linux kvm, using virtio, and the e1000, tested with sata and virtio also, so far I have no clue what the issue is, even the Proxmox host gets the same slow upload.. So I did some iperf testing and...