Hello, Proxmox users !
we experience the same problems on windows 2016, windows 2019 and windows 2022 guests.
At some point in time in Jan 2022 after windows updates, this "windows won't boot" behaviour stated to show up.
It happend last time yesterday on proxmox-ve: 7.3-1 (running kernel...
Just a note, because I had a similar problem : should your VM use a VirtIO disk instead of SATA, you must also load the VirtIO drivers from command prompt, before attempting the "bootrec" commands in repair mode :
drvload f:\viostor\2k12R2\amd64\viostor.inf
I have a similar "L3 cache" output between host and VM. But I don't think it can explain our cpu performance issues.
On top of that, our benchmarks revealed issues when testing directly on the host, so I would still blame the old RHEL kernel+patches.
Although it is not exactly the same hardware, your are perhaps hitting this proxmox-openvz-kernel bug (http://forum.proxmox.com/threads/14800-pve-%28host%29-vs-ubuntu-performance), where it basically runs as if the hyperthreaded cores were disabled.
If you are still able to carry out some quick...
I suppose that with the balance-rr to 802.3 ad scenario, the switch computes (with its internal algorithm) a different hash between the two input ports (even if the MAC address of the input bond shall be the same), as a consequence, the output port is different, so you have double bandwidth...
It will balance TCP connections (hash with IP addresses and port numbers), so iperf -P <N> where N is >= 2 will show better performance, hence the sample below, with two 1Gb/s ethernet bondings on an HP switch with LACP :
root@proxmox:~# iperf -c nas -P 4...
Ok I found the problem, there was another switch involved (a netgear GS108E) that was dropping SYN packets sent by rpcinfo -p.
i.e. http://www.developpez.net/forums/d1218869/systemes/linux/reseau/etrange-comportement-rpcinfo/
i.e...
Sorry to excave an old post, but with fresh install of proxmox 3.1 I can reproduce this problem everytime between some Dell workstations, and a QNAP TS-469L NAS or any other linux servers/VM on the local network.
I tested a dell optiplex 745 with broadcom network chipset, and a dell T3600 with...
That is normal behaviour. LACP is designed to _balance_ bandwidth between the links, but the maximum throughput between two clients is 1Gb/s.
(What is a "client" depend on the method used to compute which link should be used in function of the layer 2/3/4 adresses ;
e.g. with layer 2 you...
If that can be of any interest, I post my lacp bonding configuration over 4 ethernet cards.
The switch MUST also be configured as LACP on theses ports.
With layer 3/4 xmit hash policy it might interestingly balance multiple tcp connections between the same hosts.
auto lo
iface lo inet...
BTW Dell R720 are great but they suffer from performance problems with current pve kernels (see there http://forum.proxmox.com/threads/14800-pve-%28host%29-vs-ubuntu-performance).
just saying ...
I re-plugged the test platform.. the virt-manager kvm command-line is the folllowing :
/usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -name dumb
-uuid 0c7cff3b-072b-8e28-a909-c502754a7fcb -nodefconfig -nodefaults -chardev...
Hello dear proxmox users, I am willing to pass-through a parallel port (via usb-to-parallel) to guest vm that is too stupid (2003 server) to use a usb-to-parallel, but functions properly when kvm gives it a ready-to-use parallel port.
It works beautifully with kvm/libvirt, but proxmox prevents...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.