Trying out Xen
-
Wouldn't that Ubuntu distro take away from your baremetal resources though in comparison to just letting the Xen installer do its thing?
oh and Scott at my home lab I setup Xen to a 16GB flash without any issues at all, it was very, very easy to do.
Like with any other linux distro it's built in with version 6.5
-
@DustinB3403 said:
The installer it's self creates the required VM to run the hypervisor.
No, that's not a good description. It converts the running Ubuntu instance into the Dom0. Exactly how HyperV works as well.
-
Maybe this will help.
XenServer install = Live CD installing CentOS 6 AND Xen
Traditional Xen install = Install your preferred version of Linux, then install Xen into that.
Both must have a base Linux install called Dom0
-
@DustinB3403 said:
Wouldn't that Ubuntu distro take away from your baremetal resources though in comparison to just letting the Xen installer do its thing?
How? Xen is a bare metal OS. The Ubuntu is the Dom0 that you can't avoid no matter how you install. Xen controls all of the resources. Yes the Dom0 uses a small amount of them, but always the same amount where you install this way or install from CentOS 6 like XenServer does.
XenServer installs identically, it just doesn't show you the process as it is all automated.
-
@DustinB3403 said:
oh and Scott at my home lab I setup Xen to a 16GB flash without any issues at all, it was very, very easy to do.
I know that @Mike-Ralston was working on that a bit and was having issues with the install. Maybe he didn't try between 6.2 and 6.5.
-
I never though of using Ubuntu as Dom0 all of the documentation I read when getting everything setup recommended letting the installer create Dom0 for you.
Isn't that best practice, rather than installing your own Dom0?
-
@scottalanmiller said:
No, that's not a good description. It converts the running Ubuntu instance into the Dom0. Exactly how HyperV works as well.
I thought the standalone HyperV didn't have a Dom0 OS - that it was exactly like ESXi, just a smallish Baremetal install.
-
@Dashrender said:
I thought the standalone HyperV didn't have a Dom0 OS - that it was exactly like ESXi, just a smallish Baremetal install.
Nope, nothing would work that way for two reasons:
- You would never offer the penalty of a Dom0 if you didn't need it. That would be crazy. Getting to VMware's approach is the holy grail of hypervisor design.
- You would never engineer a product in two ways like that, it would cost a fortune.
-
This is the patching scripts we use in our Environment (work and personal) https://github.com/dalgibbard/citrix_xenserver_patcher
Love this platform, just so many amazing items.
-
@scottalanmiller said:
@Dashrender said:
I thought the standalone HyperV didn't have a Dom0 OS - that it was exactly like ESXi, just a smallish Baremetal install.
Nope, nothing would work that way for two reasons:
- You would never offer the penalty of a Dom0 if you didn't need it. That would be crazy. Getting to VMware's approach is the holy grail of hypervisor design.
- You would never engineer a product in two ways like that, it would cost a fortune.
Wow - not that I don't believe you, but well - I guess I don't. I'll have to try this for myself.
The reason I say this is because you can install HyperV without a Windows Server license, but I don't think you can install HyperV 'as a service' in a pre existing Windows Server install without one.
If you are forced to get a Dom0 Windows VM with HyperV, then how can you avoid the license requirement?
-
@DustinB3403 said:
I never though of using Ubuntu as Dom0 all of the documentation I read when getting everything setup recommended letting the installer create Dom0 for you.
Isn't that best practice, rather than installing your own Dom0?
This is all misunderstanding of how Xen works. There is one and only one way to install Xen. A Linux (or NetBSD) OS is installed. Xen installation takes that existing OS and assigns it as Dom0. Xen is installed and set to boot. System reboots to Xen with the former OS as the Dom0.
Ubuntu, OpenSuse, roll your own, XenServer... they all do this identically.
HyperV is the same. No matter what version you choose or how it appears you are installing, the exact same process happens.
-
@DustinB3403 said:
Isn't that best practice, rather than installing your own Dom0?
You can't install your own Dom0 in the way that you are thinking. The original OS is always the Dom0. Has to be because that is where the drivers and such are.
-
@scottalanmiller said:
@DustinB3403 said:
Isn't that best practice, rather than installing your own Dom0?
You can't install your own Dom0 in the way that you are thinking. The original OS is always the Dom0. Has to be because that is where the drivers and such are.
Holy cow - that statement has answered a question I've had forever regarding how drivers are handled in HyperV vs ESXi... thanks for that!
-
@scottalanmiller said:
@DustinB3403 said:
oh and Scott at my home lab I setup Xen to a 16GB flash without any issues at all, it was very, very easy to do.
I know that @Mike-Ralston was working on that a bit and was having issues with the install. Maybe he didn't try between 6.2 and 6.5.
Would it be just as advantageous to use a small ssd? Like a 24 gig mSATA or something?
-
@johnhooks said:
Would it be just as advantageous to use a small ssd? Like a 24 gig mSATA or something?
Not from a technology standpoint. Only if you owned it already and it was useless and just laying around.
-
@johnhooks said:
@scottalanmiller said:
@DustinB3403 said:
oh and Scott at my home lab I setup Xen to a 16GB flash without any issues at all, it was very, very easy to do.
I know that @Mike-Ralston was working on that a bit and was having issues with the install. Maybe he didn't try between 6.2 and 6.5.
Would it be just as advantageous to use a small ssd? Like a 24 gig mSATA or something?
That would require an mSATA port in the server and cost more than a SD card or USB stick - so why bother with the expense?
-
@Dashrender said:
The reason I say this is because you can install HyperV without a Windows Server license, but I don't think you can install HyperV 'as a service' in a pre existing Windows Server install without one.
What does the license have to do with the technology?
-
@Dashrender said:
@johnhooks said:
@scottalanmiller said:
@DustinB3403 said:
oh and Scott at my home lab I setup Xen to a 16GB flash without any issues at all, it was very, very easy to do.
I know that @Mike-Ralston was working on that a bit and was having issues with the install. Maybe he didn't try between 6.2 and 6.5.
Would it be just as advantageous to use a small ssd? Like a 24 gig mSATA or something?
That would require an mSATA port in the server and cost more than a SD card or USB stick - so why bother with the expense?
The drives are only around ~$20-$30. Same for the enclosure. I just figured you'd gain some performance from it.
-
@scottalanmiller said:
@Dashrender said:
The reason I say this is because you can install HyperV without a Windows Server license, but I don't think you can install HyperV 'as a service' in a pre existing Windows Server install without one.
What does the license have to do with the technology?
Nothing of course - but legally you can deploy HyperV without owning a single Windows Server license. If what you're saying about Dom0 is true though - wouldn't that be a Windows install, and therefore require a server license?
Now perhaps it's not a full windows install, instead it's a core install, but not core, some super stripped down core install that can't be made to do anything else, and therefore bypassing the licensing issue.
And I'll fully admit that's completely plausible.
-
@Dashrender said:
If you are forced to get a Dom0 Windows VM with HyperV, then how can you avoid the license requirement?
Because you don't "get" a Dom0. The HyperV installer obviously creates it as part of the process or would not work, just like ESXi did before ESXi 5 when they would create a Dom0 and put RHEL 2.1 into it. It was part of the package.
HyperV's included Dom0 is not Windows Server or Windows Desktop, it is an incredibly stripped Windows OS that is not available on its own in any way. It exists only with HyperV and there is no Microsoft licensing associated with it. You can't do anything with it except for manage HyperV, which if you look at MS licensing is always free, no matter how you acquire the Windows instance that you are using as the Dom0 it always ends up free. This is why. The licensing is consistent and incredibly straightforward, as long as you understand what is going on. If you fight the "Dom0" idea, all MS licensing becomes insane and makes no sense and there is no way to predict it.
