Trying out Xen
-
@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?
