Jump to content

Multiple OSes at the same time

2 hours ago, goatedpenguin said:

And even with a type 1 HV there is still the host OS between no?

No, that's the whole difference between type-1 and type-2.

 

Placing the scheduler on the same level as your guests isn't going to make any relevant difference.

 

Your guest should already run at somewhere above 90% native performance with a type-1 HV.

Remember to either quote or @mention others, so they are notified of your reply

Link to comment
Share on other sites

Link to post
Share on other sites

6 minutes ago, Eigenvektor said:

No, that's the whole difference between type-1 and type-2.

 

Placing the scheduler on the same level as your guests isn't going to make any relevant difference.

 

Your guest should already run at somewhere above 90% native performance with a type-1 HV.

Do you have any experience of hypervisor-1 and is there a default hypervisor-1 with quest-os? 

 

What i know of is XCP-NG although it's not what i want.

 

And QubeOS although i dislike tor and their network management. I kinda want to use my own network management like pfsense or openwrt.

 

Maybe you know a source.

I'm jank tinkerer if it works then it works.

Regardless of compatibility 🐧🖖

Link to comment
Share on other sites

Link to post
Share on other sites

9 hours ago, Blue4130 said:

Replace scheduler with type 1 hypervisor. That is how a type one hypervisor works. Maybe this picture will explain it better for you.

 

207785d1539195078t-hypervisor-type-1-typ

 

 

But for type 1 only one OS gets access to the full gpu and the only way the other can is through the second gpu as a passthrough

Link to comment
Share on other sites

Link to post
Share on other sites

4 hours ago, goatedpenguin said:

and the only way the other can is through the second gpu as a passthrough

This isn't strictly true; you can "passthrough" GPU control between multiple clients, as long as one of them isn't windows that is on all the time, even the then I'm pretty sure my inability to "disconnect it without summoning the BSOD demon" could be sidestepped by windoze people who know what they are doing.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×