Trying out Xen
-
@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.
-
@johnhooks said:
@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.
Once the hypervisor loads it rarely goes back to disk - it runs from RAM.
-
@Dashrender said:
@johnhooks said:
@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.
Once the hypervisor loads it rarely goes back to disk - it runs from RAM.
Oh, I misunderstood. Ok, makes more sense.
-
@johnhooks said:
The drives are only around ~$20-$30. Same for the enclosure. I just figured you'd gain some performance from it.
Nope, less than one second, on system boot only, is the best case advantage and likely not even that.
Based on VMware ESXi but the logic still applies:
http://mangolassi.it/topic/5392/why-we-run-vmware-esxi-from-sd-or-usb
-
@Dashrender said:
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.
Exactly. Microsoft has the included stripped option for "pure" HyperV installs. They have a desktop option for controlling with Windows 8 or higher. And they have a server option for controlling with Windows Server. All of which are free!!
Obviously the included one with HyperV is the best as it is the lightest and most stable/secure and requires the fewest patches. Hence why installing the "free" HyperV has always been recommend even when you own Windows Server licenses.
-
@scottalanmiller said:
@Dashrender said:
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.
Exactly. Microsoft has the included stripped option for "pure" HyperV installs. They have a desktop option for controlling with Windows 8 or higher. And they have a server option for controlling with Windows Server. All of which are free!!
Obviously the included one with HyperV is the best as it is the lightest and most stable/secure and requires the fewest patches. Hence why installing the "free" HyperV has always been recommend even when you own Windows Server licenses.
OK great, thanks for the explanation - and I now know how the driver thing is handled in HyperV for the hardware.... damn that one's haunted me for several years.
-
@Dashrender said:
OK great, thanks for the explanation - and I now know how the driver thing is handled in HyperV for the hardware.... damn that one's haunted me for several years.
LOL. That's why I always recommend installing Xen without XenServer as a learning experience. Once you've done that the "old fashioned way" and see how it works, it makes how all bare metal hypervisors work really obvious and "just make sense." It exposes everything rather than HyperV or XenServer that hide tons of the process from you so that you can't figure out what is going on.
-
@scottalanmiller said:
@Dashrender said:
OK great, thanks for the explanation - and I now know how the driver thing is handled in HyperV for the hardware.... damn that one's haunted me for several years.
LOL. That's why I always recommend installing Xen without XenServer as a learning experience. Once you've done that the "old fashioned way" and see how it works, it makes how all bare metal hypervisors work really obvious and "just make sense." It exposes everything rather than HyperV or XenServer that hide tons of the process from you so that you can't figure out what is going on.
While I understand why you say that, I'd say that @DustinB3403 lack of understanding that shows that he understood that installing Xen would produce a Dom0, he didn't understand that installing XenServer did the same.
-
@scottalanmiller This is the way I like to learn... Do it the hard way a time or two before actually doing it the easy way...
-
OK so this has been bugging me for some time, and its how Xen manages orphaned vDisks.
Specifically why does it create and leave these 0 GB disks on the system with no association to a VM?
