Proxmox VE 6.1 + VM con W10 + VirtIO

[AlfonsL]

I need your help, I can't get a VM to:


+ W10 and all updates

+ Promox VE 6.1 with all its updates

+ Virtio as they say to make it go faster, according to this tutorial https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

+ guest-agent

+ Ballon, according to this tutorial https://www.proxmox.com/en/training/video-tutorials/item/install-windows-2016-server-on-proxmox-ve

+ PCI Device Manager, according to this tutorial https://www.proxmox.com/en/training/video-tutorials/item/install-windows-2016-server-on-proxmox-ve



And nothing, W10 does not run, it is 50% slower than on my laptop where I only use W10.
I am using a DELL R710 server, with 2 Xeon and 128 GB RAM, with a 500 Gb SSD hard drive, without RAID, just to test that the W10 configuration is the most optimal.



Could someone tell me what adjustments should be made to improve the performance of a VM with W10?

Thank you.

 

[LnxBil]

And nothing, W10 does not run, it is 50% slower than on my laptop where I only use W10.

With respect to what? We need numbers.

 

[AlfonsL]

With respect to what? We need numbers.

I need a VM with W10 because I program in Xamarin + VisualStudio and it can only be done under W10 and not on Linux.
In general, everything is slower than normal, comparing it with my laptop, and that I am testing it with a DELL R710, with 2 Xeon and 128 Gb of RAM, with an SSD hard drive.
There is something of the VM definition for W10 that I am doing wrong, but I don't know what other parameters to adjust.
Tell me what instructions you want me to run so you can review my configuration or I give you access via TeamViewer or Remote Desktop and you advise me, because I have been testing and testing for days like this.
Thank you very much for your collaboration

 

[Domino]

I think if you sign up for subscriptiong/paid-support, then the techies will come to your rescue.
Otherwise the best thing you can do is browse these forums and google (which I'm guessing you already are based on the links you mentioned).

Performance totally depends on hardware and the associated tweaks per the type of hardware, how many hosts (ie cluster), remote storage (san etc), local storage (nvme? thinpool? pci disk? etc etc)...

Far too many variables.

If you are doing windows, and you just want everything to work as best performance it can, then go with Hyper-V. KVM is more designed for specific rollouts and for those who want to customise things to their use-case. Think of Proxmox like an administrators interface to KVM but without all the bells and whistles of optimisations for every conceivable hardware configuration > which is where the sysadmin/you come in and track down every bit of info you can on your hardware and in some cases even not be able to track down the info and just have to type away and build your own kernel and even your own drivers in some rare hardware scenarios.

My point... Proxmox doesn't provide an end-to-end solution, it is designed to provide a great gateway into KVM and has helped popularise KVM thanks to its ease-of-use (which I adore!), and over time it will be gifted more and more features/tweakability via the UI depending on the popularity of such use-cases.

You probably knew all of the above already, but I thought I'd just highlight the fact that nobody in the Proxmox community is going to remote into your setup to help you out, unless you're willing to pay for it, because its not a one minute job, takes a lot of testing to get it just right for any particular setup and even then it might not achieve the results you desire simply because of your hardware and overall topology.

PS. I charge $150 an hour for any tech related assistance, but have to be paid upfront, and this does not come with a guarantee that you will get what you want, simply because software alone sometimes doesnt cut it.

Try Hyper-V, if you need gpu passthrough, just get a quadro P series or an amd card, you'll get the best speed you can out of your hardware without having to do any tweaking, but this doesnt mean you'll get faster than Proxmox (after proxmox tweaking) but in general Hyper-V does achieve great speeds as long as you keep to Windows guests.

 

[AlfonsL]

I think if you sign up for subscriptiong/paid-support, then the techies will come to your rescue.
Otherwise the best thing you can do is browse these forums and google (which I'm guessing you already are based on the links you mentioned).

Performance totally depends on hardware and the associated tweaks per the type of hardware, how many hosts (ie cluster), remote storage (san etc), local storage (nvme? thinpool? pci disk? etc etc)...

Far too many variables.

If you are doing windows, and you just want everything to work as best performance it can, then go with Hyper-V. KVM is more designed for specific rollouts and for those who want to customise things to their use-case. Think of Proxmox like an administrators interface to KVM but without all the bells and whistles of optimisations for every conceivable hardware configuration > which is where the sysadmin/you come in and track down every bit of info you can on your hardware and in some cases even not be able to track down the info and just have to type away and build your own kernel and even your own drivers in some rare hardware scenarios.

My point... Proxmox doesn't provide an end-to-end solution, it is designed to provide a great gateway into KVM and has helped popularise KVM thanks to its ease-of-use (which I adore!), and over time it will be gifted more and more features/tweakability via the UI depending on the popularity of such use-cases.

You probably knew all of the above already, but I thought I'd just highlight the fact that nobody in the Proxmox community is going to remote into your setup to help you out, unless you're willing to pay for it, because its not a one minute job, takes a lot of testing to get it just right for any particular setup and even then it might not achieve the results you desire simply because of your hardware and overall topology.

PS. I charge $150 an hour for any tech related assistance, but have to be paid upfront, and this does not come with a guarantee that you will get what you want, simply because software alone sometimes doesnt cut it.

Try Hyper-V, if you need gpu passthrough, just get a quadro P series or an amd card, you'll get the best speed you can out of your hardware without having to do any tweaking, but this doesnt mean you'll get faster than Proxmox (after proxmox tweaking) but in general Hyper-V does achieve great speeds as long as you keep to Windows guests.

Thank you so much for responding so quickly,
If you already look in the proxmox forums and in google about Proxmox + W10 and many people complain about the low performance of W10 in a VM with proxmox. and that's why I had almost decided to go for Hyper-V, but before making that decision, I wanted to know if it was possible to improve the performance if there were some parameterization values to improve the performance in W10, due to widespread complaints about the poor performance .
Well, if Proxmox I see it more focused on VM with Linux and for VM with w10 I will go for Hyper-V.
At least I hope that this thread of the forum will be useful for other Proxmox users who are looking to "improve the performance of W10 in a VM with Proxmox" and realize that it is either very difficult to adjust so many parameters in Proxmox that is better than they opt for the free version of Hyper-V and that I found in this link in case anyone can use it.
https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2012-r2
Thanks for your time.

 

[Domino]

No problem, I do have a gazillion tweaks myself, and honestly I lost track of half of them!... but nowadays I'm trying to keep all my tweaks in a script so that I can easily take it across to other identical server setups. I also have a Hyper-V environment, and that is rock solid, been running since Windows 2008, through the upgrades, from Gen1 to Gen2, SRIOV plus passthrough etc... and yes Windows desktop always feels snappier for some reason on Hyper-V, but this can also be achieved with Proxmox by changing a few things in the PVE kernel, but then this also means you could lose energy efficiency too etc., its always a challenge between functionality/stability/manageability vs raw-performance, and the more you go into it the more you realise that KVM really is better suited to Linux Server VMs though Windows/Linux desktop support is great, just doesnt give you that raw performance feeling without the aforementioned tweaks which come at other costs. Proxmox is generally more stable with pcie passthrough and SRIOV, Hyper-V has its moments if you like to tinker on the go.

Personally in my opinion I find Proxmox/KVM is a production class Linux Hypervisor and Hyper-V is a production class Windows Hypervisor, though both can run either platform, they have their advantages and disadvantages on both sides... one great advantage Proxmox/KVM has over Hyper-V and VMware is the ability to (do it yourself or) hire skilled individuals to customise the whole solution for a particular use-case. Hyper-V and VMware are closed source and you're always going to be at the mercy of their respective directions/agendas (ie Vmware licensing costs and hardware support).

Oh and what I absolutely love about KVM, I get to decide what mitigations I want or don't want... got me a small performance boost just by disabling a few mitigations (ie Spectre)... (the older the cpu, the greater the boost) in windows guests you can run the tool from https://www.grc.com/inspectre.htm as administrator to disable the spectre mitigation too. Some would say you shouldnt do that, so its up to you. My opinion is that unless you're holding all your banking details and great industry secrets, your VM doesn't need protection, restore back from an off-server snapshot whenever you need to... someone said that you have a greater probability of a plane falling on your house...who knows, but quite a few fight over this argument, the crazy-pro-security lot vs the chillout-not-the-end-of-the-world lot... if you have the latest all singing dancing hardware, then the benefit of disabling is hardly noticeable, but on older hardware (which homelabs tend to run) I'd argue its a personal choice, just be smart about it.

The best way to get to grips with Proxmox is by running it as a test-bed and tweaking away with it, have a spare server where you can just throw in hardware as and when until you understand how the KVM and Linux platform all hold together... meanwhile you can have Hyper-V running on another server doing what you need... until you match the performance or better it or even just get to a point you feel comfortable with Proxmox, then you can move over. Many did the same with production migrations from VMware/HyperV to Proxmox too, there is a learning curve, and as I said earlier, if you have a bursting wallet or a great budget (ie a business), then one can easily hire Proxmox/KVM techs to assist in rollouts/migrations and also purchase support contracts too.

The fantastic thing about Proxmox is that it is open-source, and what that means is that homelab'ers or sysadmins with time on their hands can get right in there and tweak away, it is half the enjoyment of Linux afterall, actually being able to see the code and change a thing here and there for personal needs!

 

[AlfonsL]

[QUOTE = "Domino, publicación: 313975, miembro: 93049"]
No hay problema, ¡tengo miles de millones de ajustes, y honestamente perdí la noción de la mitad de ellos! ... pero hoy en día estoy tratando de mantener todos mis ajustes en un script para poder llevarlos fácilmente a otro servidor idéntico configuraciones. También tengo un entorno Hyper-V, y es muy sólido, he estado funcionando desde Windows 2008, a través de las actualizaciones, de Gen1 a Gen2, SRIOV más passthrough, etc ... y sí, el escritorio de Windows siempre se siente más ágil por alguna razón en Hyper- V, pero esto también se puede lograr con Proxmox cambiando algunas cosas en el kernel PVE, pero esto también significa que también podría perder la eficiencia energética, etc., siempre es un desafío entre funcionalidad / estabilidad / capacidad de administración versus rendimiento bruto, y cuanto más entras en él, más te das cuenta de que KVM realmente se adapta mejor a las máquinas virtuales del servidor Linux, aunque el soporte de escritorio de Windows / Linux es excelente, simplemente no te da esa sensación de rendimiento sin los ajustes mencionados que conllevan otros costos. Proxmox es generalmente más estable con pcie passthrough y SRIOV, Hyper-V tiene sus momentos si le gusta jugar sobre la marcha.

Personalmente, en mi opinión, creo que Proxmox / KVM es un hipervisor de Linux de clase de producción y Hyper-V es un hipervisor de Windows de clase de producción, aunque ambos pueden ejecutar cualquier plataforma, tienen sus ventajas y desventajas en ambos lados ... una gran ventaja Proxmox / KVM tiene más de Hyper-V y VMware es la capacidad de (hacerlo usted mismo o) contratar a personas calificadas para personalizar la solución completa para un caso de uso particular. Hyper-V y VMware son de código cerrado y siempre estará a merced de sus respectivas direcciones / agendas (es decir, costos de licencia de Vmware y soporte de hardware).

Ah, y lo que me encanta de KVM, puedo decidir qué mitigaciones quiero o no quiero ... obtuve un pequeño aumento en el rendimiento al deshabilitar algunas mitigaciones (es decir, Spectre) ... (cuanto mayor es la CPU, cuanto mayor sea el impulso) en los invitados de Windows, puede ejecutar la herramienta desde https://www.grc.com/inspectre.htmcomo administrador para deshabilitar la mitigación del espectro también. Algunos dirían que no debes hacer eso, así que depende de ti. Mi opinión es que, a menos que tenga todos sus datos bancarios y grandes secretos de la industria, su VM no necesita protección, restablezca desde una instantánea fuera del servidor cada vez que lo necesite ... alguien dijo que tiene una mayor probabilidad de un avión que cae sobre tu casa ... quién sabe, pero bastantes peleas por este argumento, el lote loco-pro-seguridad frente al lote chillout-not-the-end-of-the-world ... si tienes lo último en hardware para cantar y bailar, entonces el beneficio de la desactivación apenas se nota, pero en hardware más antiguo (que los homelabs tienden a funcionar) diría que es una elección personal, solo sé inteligente al respecto.

La mejor manera de familiarizarse con Proxmox es ejecutarlo como un banco de pruebas y modificarlo, tener un servidor de repuesto donde pueda colocar el hardware como y hasta que comprenda cómo se unen las plataformas KVM y Linux. ... mientras tanto, puede hacer que Hyper-V se ejecute en otro servidor haciendo lo que necesita ... hasta que iguale el rendimiento o lo mejore o incluso llegue a un punto en el que se sienta cómodo con Proxmox, luego puede moverse. Muchos hicieron lo mismo con las migraciones de producción de VMware / HyperV a Proxmox también, hay una curva de aprendizaje y, como dije antes, si tiene una billetera explosiva o un gran presupuesto (es decir, un negocio), entonces uno puede contratar fácilmente Proxmox / Técnicos de KVM para ayudar en implementaciones / migraciones y también comprar contratos de soporte también.

Lo fantástico de Proxmox es que es de código abierto, y lo que eso significa es que los trabajadores en el hogar o administradores de sistemas con tiempo en sus manos pueden entrar y modificar, es la mitad del disfrute de Linux después de todo, realmente poder para ver el código y cambiar algo aquí y allá para necesidades personales!
[/CITAR]

 

[AlfonsL]

[QUOTE = "Domino, publicación: 313975, miembro: 93049"]
No hay problema, ¡tengo miles de millones de ajustes, y honestamente perdí la noción de la mitad de ellos! ... pero hoy en día estoy tratando de mantener todos mis ajustes en un script para poder llevarlos fácilmente a otro servidor idéntico configuraciones. También tengo un entorno Hyper-V, y es muy sólido, he estado funcionando desde Windows 2008, a través de las actualizaciones, de Gen1 a Gen2, SRIOV más passthrough, etc ... y sí, el escritorio de Windows siempre se siente más ágil por alguna razón en Hyper- V, pero esto también se puede lograr con Proxmox cambiando algunas cosas en el kernel PVE, pero esto también significa que también podría perder la eficiencia energética, etc., siempre es un desafío entre funcionalidad / estabilidad / capacidad de administración versus rendimiento bruto, y cuanto más entras en él, más te das cuenta de que KVM realmente se adapta mejor a las máquinas virtuales del servidor Linux, aunque el soporte de escritorio de Windows / Linux es excelente, simplemente no te da esa sensación de rendimiento sin los ajustes mencionados que conllevan otros costos. Proxmox es generalmente más estable con pcie passthrough y SRIOV, Hyper-V tiene sus momentos si le gusta jugar sobre la marcha.

Personalmente, en mi opinión, creo que Proxmox / KVM es un hipervisor de Linux de clase de producción y Hyper-V es un hipervisor de Windows de clase de producción, aunque ambos pueden ejecutar cualquier plataforma, tienen sus ventajas y desventajas en ambos lados ... una gran ventaja Proxmox / KVM tiene más de Hyper-V y VMware es la capacidad de (hacerlo usted mismo o) contratar a personas calificadas para personalizar la solución completa para un caso de uso particular. Hyper-V y VMware son de código cerrado y siempre estará a merced de sus respectivas direcciones / agendas (es decir, costos de licencia de Vmware y soporte de hardware).

Ah, y lo que me encanta de KVM, puedo decidir qué mitigaciones quiero o no quiero ... obtuve un pequeño aumento en el rendimiento al deshabilitar algunas mitigaciones (es decir, Spectre) ... (cuanto mayor es la CPU, cuanto mayor sea el impulso) en los invitados de Windows, puede ejecutar la herramienta desde https://www.grc.com/inspectre.htmcomo administrador para deshabilitar la mitigación del espectro también. Algunos dirían que no debes hacer eso, así que depende de ti. Mi opinión es que, a menos que tenga todos sus datos bancarios y grandes secretos de la industria, su VM no necesita protección, restablezca desde una instantánea fuera del servidor cada vez que lo necesite ... alguien dijo que tiene una mayor probabilidad de un avión que cae sobre tu casa ... quién sabe, pero bastantes peleas por este argumento, el lote loco-pro-seguridad frente al lote chillout-not-the-end-of-the-world ... si tienes lo último en hardware para cantar y bailar, entonces el beneficio de la desactivación apenas se nota, pero en hardware más antiguo (que los homelabs tienden a funcionar) diría que es una elección personal, solo sé inteligente al respecto.

La mejor manera de familiarizarse con Proxmox es ejecutarlo como un banco de pruebas y modificarlo, tener un servidor de repuesto donde pueda colocar el hardware como y hasta que comprenda cómo se unen las plataformas KVM y Linux. ... mientras tanto, puede hacer que Hyper-V se ejecute en otro servidor haciendo lo que necesita ... hasta que iguale el rendimiento o lo mejore o incluso llegue a un punto en el que se sienta cómodo con Proxmox, luego puede moverse. Muchos hicieron lo mismo con las migraciones de producción de VMware / HyperV a Proxmox también, hay una curva de aprendizaje y, como dije antes, si tiene una billetera explosiva o un gran presupuesto (es decir, un negocio), entonces uno puede contratar fácilmente Proxmox / Técnicos de KVM para ayudar en implementaciones / migraciones y también comprar contratos de soporte también.

Lo fantástico de Proxmox es que es de código abierto, y lo que eso significa es que los trabajadores en el hogar o administradores de sistemas con tiempo en sus manos pueden entrar y modificar, es la mitad del disfrute de Linux después de todo, realmente poder para ver el código y cambiar algo aquí y allá para necesidades personales!
[/CITAR]

Thank you very much for answering my thread.
I love Proxmox, it weighs little and is very friendly.
But I see that the marriage between Proxmox and W10 is not very good.
And isn't there a tutorial on what parameters should be adjusted in Proxmox so that a VM with W10 can work agilely?
There are many people who complain about the performance of W10 with Proxmox, so I think that if someone could adjust it properly, they could tell the community that it has to be adjusted.
In case anyone might be interested, I want to use W10 with Xamarin and VisualStudio, in order to generate APP for Android, with which I need Proxmox to be able to work agilely when compiling the APP, with only one SSD disk.
Thank you very much to all the community

 

[Domino]

There are a few discussions out there... here's one from a couple of years ago... but it will require you to recompile the kernel with certain flags set.

https://www.reddit.com/r/VFIO/comments/84181j/how_i_achieved_under_1ms_dpc_and_under_025ms_isr/

However it doesnt go into details on how to actually do the compile etc, this you will have to research yourself and again there are bits of info here and there which you will have to assimilate.

Also do keep in mind, once you compile your own kernel, Proxmox team won't be able to support you, so keep in mind that once you go down the unofficial route, you're the master of your own results and research, though I'm sure some here and there may add a pointer here and there for reference info but other than that you're on your own.

 

[LnxBil]

Wow. Good discussion. Thank you @Domino for sharing.

There is something of the VM definition for W10 that I am doing wrong, but I don't know what other parameters to adjust.

Normally, if you select Windows 10 in PVE, the settings are already optimized (with respect to what you can select in the PVE GUI). I also run ca. 20 Windows 10 in there and you cannot expect performance out of them. It's slow, often dead slow even with high class enterprise hardware. I also don't know why, but mainly due to GPU stuff, so even Windows is very slow nowadays without proper gpu acceleration. The windows servers are another matter, you don't need the GUI there and they perform a bit better. I also don't virtualize a lot of Linux desktops, but if so, I use X2GO or SPICE which gives a little bit of gpu performance back, but PVE - at least in my opinion - is for server workloads, not desktops. The limitation of vGPU or passthrough is a big bummer, but it's been worked on on the kvm/qemu end.
If you want to check out another KVM-based product, try unraid. It is often used for Windows Passthrough and gaming stuff like Linus'es x games, 1 pc video series.

I'd even recommend running VirtualBox but if you already have Hyper-V or a Windows 10 Prof. license, just go with it on windows. I also have to say, that we also run machines in VMware and Hyper-V and the linux guests are normally not as fast as their kvm counterparts, so kvm is not just bad as some could argue if you read this thread.

 

[AlfonsL]

There are a few discussions out there... here's one from a couple of years ago... but it will require you to recompile the kernel with certain flags set.

https://www.reddit.com/r/VFIO/comments/84181j/how_i_achieved_under_1ms_dpc_and_under_025ms_isr/

However it doesnt go into details on how to actually do the compile etc, this you will have to research yourself and again there are bits of info here and there which you will have to assimilate.

Also do keep in mind, once you compile your own kernel, Proxmox team won't be able to support you, so keep in mind that once you go down the unofficial route, you're the master of your own results and research, though I'm sure some here and there may add a pointer here and there for reference info but other than that you're on your own.

no, no, I don't want to stray from the standard.
Perhaps it would be good if Promox had examples of VM templates for W10, for those who started with Proxmox, their use will be faster.
In many forums I see that people complain about the poor performance of W10 with Proxmox, so I propose if "someone" of those who know about Proxmox could help us with templates.
Thanks for your cooperation

 

[AlfonsL]

Wow. Good discussion. Thank you @Domino for sharing.



Normally, if you select Windows 10 in PVE, the settings are already optimized (with respect to what you can select in the PVE GUI). I also run ca. 20 Windows 10 in there and you cannot expect performance out of them. It's slow, often dead slow even with high class enterprise hardware. I also don't know why, but mainly due to GPU stuff, so even Windows is very slow nowadays without proper gpu acceleration. The windows servers are another matter, you don't need the GUI there and they perform a bit better. I also don't virtualize a lot of Linux desktops, but if so, I use X2GO or SPICE which gives a little bit of gpu performance back, but PVE - at least in my opinion - is for server workloads, not desktops. The limitation of vGPU or passthrough is a big bummer, but it's been worked on on the kvm/qemu end.
If you want to check out another KVM-based product, try unraid. It is often used for Windows Passthrough and gaming stuff like Linus'es x games, 1 pc video series.

I'd even recommend running VirtualBox but if you already have Hyper-V or a Windows 10 Prof. license, just go with it on windows. I also have to say, that we also run machines in VMware and Hyper-V and the linux guests are normally not as fast as their kvm counterparts, so kvm is not just bad as some could argue if you read this thread.

Thank you very much for your comments, if that is what I am going to do. I'm going to install W10 and then Hyper-V and then create VMs with W10. I have read several articles where they say that you get good performances.
Proxmox is a very good tool, but especially if the VMs are in Linux and also for backend issues, but to be a programmer with VisualStudio + Xamarin and compile APP for Android, I personally do not recommend Proxmox VE 6.1 in case of low performance and that I have been making daily adjustments and reading forums for 2 weeks, but there is no clear line of what to adjust, there are so many variables in Proxmox, you get a little lost.
Well, nothing for W10 by installing Hyper-V, which comes for free and then create VMs with W10.
And on another server, with less hardware requirements, I will install Proxmox for backend software.
Thank you all, hopefully Proxmox could deliver Templates for W10.

 

[Domino]

Good plan @AlfonsL

Just for you, I thought I'd give it a shot and installed Windows 10 as an EFI install on my Proxmox testbed server (DL380 G9)... gave it a qcow storage file stored on my HyperV SMB server across a 100G Chelsio T6 RDMA link, chucked in a single-slot nvidia 1650, attached a long-run optical hdmi cable to my kids tv, and an active usb 3 extension lead, banged a powered usb 3 hub on that, plugged in a keyboard+mouse dongle and a broadcom chipset bluetooth dongle, paired a gamepad, paired the keyboard and mouse.

Everything works like native, yes seriously. Chucked on a few games, perfect. Proxmox baseline tuning has come a long way, but it really is by default geared for popular enterprise hardware.

I'll probably leave that setup for my kid now, and the server barely has to work for that one VM. (it has a few more VMs on it and a quadro for 3d work offloading).

My point, Proxmox works great out of the box with my server for windows guests, the only thing I had to 'tune' was the storage IO, in the end I found that SMB Direct gave me the best all-round performance, even better than using native NVME passthrough, though I did have to recompile the kernel for SMB Direct as it is disabled by default (something I hope the Proxmox maintainers may look into in the near future because it works like a champ).

In a word, Proxmox is very flexible and my son now has a good enough Windows 10 gaming pc in his room, until I scrap the server off onto ebay. Proxmox may be specifically tuned for production environments, but it doesn't mean that is its limit... its limit is always going to be the investment of time from the one who desires to tune KVM/Linux... partly why Unraid is so popular among gamers as a lot of that tuning effort is fairly public knowledge and even made it into their code.

 

[LnxBil]

Just for you, I thought I'd give it a shot and installed Windows 10 as an EFI install on my Proxmox testbed server (DL380 G9)... gave it a qcow storage file stored on my HyperV SMB server across a 100G Chelsio T6 RDMA link, chucked in a single-slot nvidia 1650, attached a long-run optical hdmi cable to my kids tv, and an active usb 3 extension lead, banged a powered usb 3 hub on that, plugged in a keyboard+mouse dongle and a broadcom chipset bluetooth dongle, paired a gamepad, paired the keyboard and mouse.

You have 100G in your home? I've never seen 100G at any company I worked for (25GBE at most, or dual 32GBit FC). Wow....

something I hope the Proxmox maintainers may look into in the near future because it works like a champ.

Have you opened a bug report for that?

 

[Domino]

The house is wired up for 10G.. I use 100G with a ToR switch for interlink between all the nodes in the rack.

Didn't report it as a bug because it doesn't appear to be a bug, it was simply disabled in the config. Maybe because upstream it is still considered 'experimental', but where I'm sitting it works perfectly for my use case.

 

[LnxBil]

The house is wired up for 10G.. I use 100G with a ToR switch for interlink between all the nodes in the rack.

Did you use copper of fiber for the inhouse routing?

Didn't report it as a bug because it doesn't appear to be a bug, it was simply disabled in the config. Maybe because upstream it is still considered 'experimental', but where I'm sitting it works perfectly for my use case

Thanks for reporting back.
Yes, I also read the other thread. I was moving from newest to oldest and this thread just came first :-D

 

[AlfonsL]

Good plan @AlfonsL

Just for you, I thought I'd give it a shot and installed Windows 10 as an EFI install on my Proxmox testbed server (DL380 G9)... gave it a qcow storage file stored on my HyperV SMB server across a 100G Chelsio T6 RDMA link, chucked in a single-slot nvidia 1650, attached a long-run optical hdmi cable to my kids tv, and an active usb 3 extension lead, banged a powered usb 3 hub on that, plugged in a keyboard+mouse dongle and a broadcom chipset bluetooth dongle, paired a gamepad, paired the keyboard and mouse.

Everything works like native, yes seriously. Chucked on a few games, perfect. Proxmox baseline tuning has come a long way, but it really is by default geared for popular enterprise hardware.

I'll probably leave that setup for my kid now, and the server barely has to work for that one VM. (it has a few more VMs on it and a quadro for 3d work offloading).

My point, Proxmox works great out of the box with my server for windows guests, the only thing I had to 'tune' was the storage IO, in the end I found that SMB Direct gave me the best all-round performance, even better than using native NVME passthrough, though I did have to recompile the kernel for SMB Direct as it is disabled by default (something I hope the Proxmox maintainers may look into in the near future because it works like a champ).

In a word, Proxmox is very flexible and my son now has a good enough Windows 10 gaming pc in his room, until I scrap the server off onto ebay. Proxmox may be specifically tuned for production environments, but it doesn't mean that is its limit... its limit is always going to be the investment of time from the one who desires to tune KVM/Linux... partly why Unraid is so popular among gamers as a lot of that tuning effort is fairly public knowledge and even made it into their code.

Hello friend, I congratulate you if you got it, because I have been reading forums and changing parameters for 2 weeks and there is no way and that I have tried everything. A great pity that I have not managed that the VM with W10 and VisualStudio and with Xamarin, in order to create an APP for Android, has managed to run smoothly.
Working works, but not quickly and smoothly, it seems that the VM has a brake and not so the NODE and the Proxmox admission that it works very smoothly.
Thank you very much mate

 

[Domino]

When we look across the web at KVM running windows guests, people all over have problems, mostly relative to latency issues, in most cases pinning cores and turning off power saving measures from bios to kernel etc seem to be the goto routes to improvement. Then there's also disabling mitigations, tweaking Windows guests themselves as in disabling system drivers, antivirus, firewall etc... and this whole process is guaranteed to be unique for virtually every unique hardware setup as well as the priority of the host, ie. many consumer use-cases hover around just wanting to have a snapshot'able desktop VM, though I'd advise just setting up an iscsi storage unit and going that route and totally avoiding virtualisation, each to their own I guess.

In my case with this Windows guest I didn't bother with any cpu pinning or tweaks. I just ran a quick dpc latency test and it seems perfect for a desktop VM, the few old 4k games I ran were butter smooth even with a 1650. I'm sure if I did some pinning here and there I could get latency right down, however it currently runs without any audio/mouse/gpu gltches whatsoever so there isn't any need really, and note this is also with a few other vms where one is even a nested Hyper-V hypervisor running 2 more vms. Everything just works, quite well might I add, did a sysbench on the nested VMs and they're only out by 20% performance of VMs outside of the nest, very nice.




One fact appears to reign supreme, motherboards and their bios can have drastic effects on virtualisation, so personally I would suggest anyone wanting to run things butter smooth to consider browsing consumer orientated Unraid forums as well as here to get an idea of what hardware (board/cpu/gpu/usb cards) and general configurations those who are running near bare-metal speed/smooth VMs are using.

Other than that, in my opinion the Windows template which Proxmox already comes with is quite optimal considering current QEMU build. Maybe in the future it would be a a benefit if Proxmox provided a core-pinning configuration user-interface for low-latency use-cases as that is currently a long-winded manual effort.