I have been searching for documentation on how to properly enable the HPET on a Hyper-V. I haven't been able to find anything specifying if it works or not, and if it does work, how to properly enable it. From our initial tests, it doesn't seem to be consistent with either the machines timer or the HPET.
We are deploying Lync and UCMA based applications and have noticed a significant performance difference between machines with HPET enable and HPET disabled in terms of their ability to handle capacity. We would like to be able to virtualize these machines, but the HPET is currently our limiting factor.
Can anyone point me in the right direction to find an answer?
I am not sure but I don't think we can enable HPET in VM .
Generally for a physical machine we can enable it
1.From BIOS enable HPET
and
2.From OS run bcdedit /set useplatformclock true and then reboot.
Looking at Microsoft's Hypervisor Top-Level Functional Specification, the only references to the HPET I can see relate to the hypervisor's own use of the HPET. It doesn't appear to provide a virtual HPET device.
Related
I am looking for an alternative to azure accelerated networking. Usecase remains the same. I wish to have better response times on my VM which has support for hyperthreading. My concern is around cpu core underutilization brought forth by the accelerated networking requirement of maintaining 4 CPUs. The application doesn't even use up 2 cores. Let me know if there are any possible solutions.
Receive Side Scaling (RSS) is one known option...
If the Windows VM supports Accelerated Networking, enabling that feature would be the optimal configuration for throughput. For all other Windows VMs, using Receive Side Scaling (RSS) can reach higher maximal throughput than a VM without RSS. RSS may be disabled by default in a Windows VM.
On Linux VMs, it is enabled by default.
Environment:
I have an embedded linux system running with an ARM based iMX7 processor. It runs on a build from yocto linux which is very much based on Fedora.
Scenario:
My system uses Suspend To RAM feature which is linux system power saving mode that is explained quite well in this link. This is done to save power at a certain stage.
Objective:
Now, I need to keep the wifi link open during this stage. And as I read from some discussions like this, it seems to be possible to do so.
How can I do this?
Read up on similar discussions:
Reading through this discussion, it explains how to do this on a intel based desktop linux computer. But I don't have the /etc/NetworkManager on my embedded linux device. Probably there is a different way to do it on a Fedora based embdded linux system.
Can I get some suggestions on how to do this or even how to approach this?
None of the articles you quoted even suggest that it is possible to leave WiFi on - in fact one of them says it can't be done. All they provide is various tricks to make the wake-up faster.
Depends on the hardware but very likely, leaving it on is really impossible. Suspend-to-ram includes a hardware command that switches the CPU clock off, places its interconnect buses into idle state, and disables main power to all the peripherals (leaving only standby power to those peripherals that support standby mode).
I don't know if your WiFi device has support for running on standby power nor whether the embedded hardware you have has the ability to provide that power to it while the CPU is off. If that ability exists, it will likely be accessible as a kernel driver parameter.
You may be able to save some startup time when waking up from standby by providing a static configuration for your WiFi device rather than using the default automatic connection (which involves searching for a router to connect to, obtaining an IP address, etc.).
You can't just keep wifi active during sleep/resume. You can optimise reconnection speed but I believe NM and connman both do that already.
I have tried looking everywhere but there seems to be no help at all regarding enabling virtualization in Win 10.
Moreover, Gigabyte 970A DS3P support is also not helping.
Any help will be much appreciated.
Thanks
Really late to the party here but someone else might need this...
To check if your CPU has Hyper-V support (and many other things) you can run coreinfo.exe written by Mark Russinovich / Sysinternals and available via MS website. It lists support for "Hypervisor" at the top of all the things it reports.
To enable Virtualization (Hyper-V) in Windows 10 you need to turn on the feature. Check out this post https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install
On the bios side. I'm not sure about the 970a. I do have a Gigabyte board and it is in the advanced section of the bios setup. I could depend on your chipset and CPU. You need a newer chipset and a supported CPU to do virtualization
Constraints:
My application requires SSE4.2 instruction set.
I am using packer.io to provision my Windows Azure VM (OpenLogic 6.5 OS.)
Windows Azure returns an AMD-processor-backed-VM about 15% of the time. The rest of the time - they are Intel-processor-based. AMD processors do not support SSE4.2, but they do support SSE4a. So, my application is terminated with SIGILL on AMD processors.
Questions:
Can I request specific architecture (Intel CPU) when Packer
provisions a VM? I know that instance types >= A8 come only with Intel processors, but they are more expensive, and I would not want to use them for development.
If Packer cannot do it, what are the other options
(Powershell, ect...) that would give me this functionality?
Thank you.
Answering my own question. Azure does not provide a way to request processor type. The only way to ensure Intel processor is to not use A-series machines (as confirmed by a MSFT representative.) Thus, no tool can do it.
I am trying to enable Hyper-V in my local machine running Windows 8 Enterprise Ed 64-bit. I checked and my hardware is SLAT-compatible, the option in BIOS is turned on. I did several cold boot but the Hyper-V platform option still remains grayed out. I hope someone can help me since all the blogs/forums that seems to address this issue did not solve the issue for me.
If you hover your mouse over the Hyper-V item in the Optional Features list, it will tell you why it's disabled.
Otherwise, you can run MSINFO32.EXE and the System Summary panel will list the features required for Hyper-V and whether or not those features have been detected on your system.
Also, you said you've cold-booted the system a few times. This might sound stupid, but shut your system down and unplug it for a few minutes to make sure it's actually off before plugging it in and turning it on again. I've never seen a system where I had to do this, but I know other people who have.
Turn on Data Exeuction Prevention ?
Control panel - System - System Properties -Data Exeuction Prevention