Random Thread - Anything Goes
-
-
-
This is why I don't use HyperV
Setup new server gave it a name and IP connected to it via HperV Manager on Windows 10 Pro machine:-
Tried 5nine when creating a switch:-
-
Do I try KVM?
Or go straight to what I know and XenServer? -
Am I right in thinking KVM is not a type 1 hypervisor as in install on the host from a iso?
You need a base Linux OS like Ubuntu then install KVM. -
@hobbit666 KVM is already built in to the fedora-branch of distros. Not sure about Ubuntu, but I would imagine so. Just have to set it up.I would also imagine that the Linux environment that you set up for initial installation would be considered Dom0.
-
@hobbit666 said in Random Thread - Anything Goes:
Am I right in thinking KVM is not a type 1 hypervisor as in install on the host from a iso?
You need a base Linux OS like Ubuntu then install KVM.Why would the way you install it not make it a type 1? When you install it on a Linux distribution the distribution becomes a VM on top of KVM. It's similar, but different, to how Xen and Hyper-V work.
-
@coliver said in Random Thread - Anything Goes:
Why would the way you install it not make it a type 1? When you install it on a Linux distribution the distribution becomes a VM on top of KVM. It's similar, but different, to how Xen and Hyper-V work.
That's why I was asking to me installing a OS then the hypervisor doesn't sound like Type1 to me, hence asking.
If it then changes the way the machine runs then yes it might be a type1
my only exposer to KVM is seeing it mentioned -
@hobbit666 said in Random Thread - Anything Goes:
@coliver said in Random Thread - Anything Goes:
Why would the way you install it not make it a type 1? When you install it on a Linux distribution the distribution becomes a VM on top of KVM. It's similar, but different, to how Xen and Hyper-V work.
That's why I was asking to me installing a OS then the hypervisor doesn't sound like Type1 to me, hence asking.
If it then changes the way the machine runs then yes it might be a type1 my only exposer to KVM is seeing it mentioned Ok, KVM is a type 1 hypervisor.
-
@hobbit666 said in Random Thread - Anything Goes:
This is why I don't use HyperV
Setup new server gave it a name and IP connected to it via HperV Manager on Windows 10 Pro machine:-
Tried 5nine when creating a switch:-
If you are connecting to Hyper-V in a workgroup environment, take a look at this link
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts -
@hobbit666 Domain joined or workgroup?
-
@hobbit666 said in Random Thread - Anything Goes:
Am I right in thinking KVM is not a type 1 hypervisor as in install on the host from a iso?
You need a base Linux OS like Ubuntu then install KVM.Installing KVM on Fedora
https://fedoraproject.org/wiki/Getting_started_with_virtualizationInstalling KVM on Ubuntu
https://help.ubuntu.com/community/KVM/Installation -
@hobbit666 said in Random Thread - Anything Goes:
Am I right in thinking KVM is not a type 1 hypervisor as in install on the host from a iso?
You need a base Linux OS like Ubuntu then install KVM.The way I understand it (and please correct me if I'm wrong) is that KVM is a kernal module that turns Linux into a type-1 hypervisor. It looks confusing because the distro you installed is still fully functional.
-
I think that KVM is considered a Type-0 hypervisor... but it's more closely related to Type-1 then it is Type-2.
-
@coliver said in Random Thread - Anything Goes:
I think that KVM is considered a Type-0 hypervisor... but it's more closely related to Type-1 then it is Type-2.
Type 0 isn't exactly a real thing. It's a informal type of type 1.
-
@wirestyle22 said in Random Thread - Anything Goes:
@hobbit666 said in Random Thread - Anything Goes:
Am I right in thinking KVM is not a type 1 hypervisor as in install on the host from a iso?
You need a base Linux OS like Ubuntu then install KVM.The way I understand it (and please correct me if I'm wrong) is that KVM is a kernal module that turns Linux into a type-1 hypervisor. It looks confusing because the distro you installed is still fully functional.
That's basically correct. Linux itself is the hypervisor.
-
@scottalanmiller said in Random Thread - Anything Goes:
@coliver said in Random Thread - Anything Goes:
I think that KVM is considered a Type-0 hypervisor... but it's more closely related to Type-1 then it is Type-2.
Type 0 isn't exactly a real thing. It's a informal type of type 1.
Ah that makes sense. I had never learned about Type 0 until I had played with KVM.
-
@hobbit666 said in Random Thread - Anything Goes:
Am I right in thinking KVM is not a type 1 hypervisor as in install on the host from a iso?
You need a base Linux OS like Ubuntu then install KVM.That's how Xen and Hyper-V install too.
-
@coliver said in Random Thread - Anything Goes:
@scottalanmiller said in Random Thread - Anything Goes:
@coliver said in Random Thread - Anything Goes:
I think that KVM is considered a Type-0 hypervisor... but it's more closely related to Type-1 then it is Type-2.
Type 0 isn't exactly a real thing. It's a informal type of type 1.
Ah that makes sense. I had never learned about Type 0 until I had played with KVM.
It's marketing. And it has changed since it isn't a real definition. VMware always wants ESXi to be the only type 0 so the definition is a moving one.
-
/rootis a directory for the root user and/is the root directory, but if you create a new user it's put under/home/username. Is this because the home directory can be put on a different parition and if it failed to mount would screw you?
