Windows 10 'end of service' message.

So in which case, you can go Programs & Features in control panel, then "turn windows features on or off", and add Hyper V etc. (it does not take long to install - but will need a reboot to complete).

Reply to
John Rumm
Loading thread data ...

With an inverted hypervisor, even the host OS uses the hypervisor, just like the guest does for some purposes. Just so you're aware of what the reboot is for. The host then "re-tools" for its new dining location. The difference between a "regular" driver for storage and a paravirtualized one, is 30MB/sec versus 600MB/sec. I expect, when Hyper-V is a permanent fixture, you will be able to detect a permanent slowdown in high speed disk access (that expensive PCIe Rev4 NVMe you bought). And part of that, will be calls going through the extra layer, as seen from the Host.

formatting link
With VirtualBox 6 (Hyper-V compatible, so-called), VirtualBox will also have to dine, via making hypervisor calls, and will be a "servant" of Hyper-V. I don't know if that's shown in the diagram.

You should also be aware, that from a performance perspective, not all software is "positionally agnostic". If you're using, say, Ubuntu, you use Synaptic, you install a package, one of the steps is to update all the manual pages on the system. If run from Ring 3 (a "normal Host"), this runs at a good speed, and behaves as it should. If the same Ubuntu install is moved, via P2V, into a Ubuntu Guest, and a package is installed, the manual page updater runs at a slugs pace. And that's because the author of the manual page updater, has done something "sooper-secure" to the manual page updating process. It notices what Ring its in, and changes methods or something. I was not able to find the source that was doing that. Presumably some service that code calls, is responsible for differential behavior.

This is generally a problem with a highly-virtualized world -- when there is a performance problem, you will be f***ed trying to find the root cause and do something about it. When someone (a developer!) wanted help with debugging a performance issue with a Snap, I discovered there was absolutely nothing I could do to help. All I could do was sit and stare out the window. Such is what will be a common situation, in a containerized/virtualized world. Between the Snaps and the Hyper-V, we won't have a clue what's going on. Microsoft will have its WSL2, Linux supported by WSL2 will have its own kernel, its own scheduler or whatever. We will be relying on those lazy bastards at Microsoft, to test stuff... and you know how *that's* going to work out. They couldn't test their way out of a wet paper bag (see Windows Update experiences for evidence).

And no, the answer is not "to buy a faster processor" :-) Although I expect jokes to that effect. "If only I had a faster processor, this shambles wouldn't be a problem..."

Paul

Reply to
Paul

I have generally found that the current Hyper V setup is pretty low impact. I doubt it even reduces real world performance for clients by more than 5%

(I can still get > 2GB/sec sequential read speeds from a NVMe SSD...)

Yup since WSL2, the whole lot integrates much better - although as you say other hypervisors are in effect now hyper V clients.

:-)

(although I did upgrade recently to a less power hungry CPU - also had the bonus of big boost in speed!)

Reply to
John Rumm

I have this on a 2 year old computer - win 10 home 64bit.

Reply to
alan_m

Maybe the problem is that the modern versions have a million extra widgets where the majority are not used or required. And then with every update the user interface is changed :( Do you remember the time when a word processor came on a single floppy disk and did everything that most businesses and personal users required?

Reply to
alan_m

Hasn't this been the reason for so many software outages when bank and building society try and modify the 20/30 year old software they are still using.

Reply to
alan_m

Win 10 typically does two substantial updates per year, these are called "feature updates" rather than the regular weekly "quality updates" (bug fixes and security updates etc).

You can avoid[1] installing the feature updates for some time if you want. However there comes a time where they cease supporting the older feature update versions (typically 18 months after release).

Note that you need to be on a supported feature update to continue to receive quality updates. So ultimately there is significant incentive to move to a current feature version. Welcome to SaaS!

[1] You can avoid on "Pro", "Enterprise", "IoT", "Education" versions, but not "Home".
Reply to
John Rumm

In my first job, I produced some datasheets that had IBM box characters to make tables. They were created on an IBM AT, using WordStar. The Epson printer could not print these characters though, so to print those documents, I used to go down to the shopfloor, with a single, 5-1/4",

360K floppy disk, containing all of Wordstar (except the thesaurus) and my documents and "borrow" the PC and printer used for label production.
Reply to
Steve Walker

Well I can go back further than that but not with MSDOS, or even CP/M

It's not the databases that are the issue, it is the software application behind it, and some fairly sophisticated which I'm in no mood to rewrite in whatever is today's flavour of the month language. The programs still do what they were designed to do, or would if I could readily run them.

Reply to
AnthonyL

Well understood. Add RM-Cobol to that mix as well.

Reply to
AnthonyL

HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.