Dashrender why did you migrate to Hyper-V from XenServer
-
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
-
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
-
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
-
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
New to this purpose - yes... so I set it up with Hyper-V 2019 (yeah JB is spinning in his grave).
My old XenServer box needed to die - so I moved the VM to Hyper-V and killed it.
I didn't really care about XenServer/XCP-ng - so meh. I feel/felt I needed some hands on experience in Hyper-V, Plus I do have an AD environment, so I used Hyper-V. that's the long and the short. Ultimately I don't really give a shit which hypervisor I use. I might bail on it later.. I truly dislike the single pain of glass management of Hyper-V (at least without VMM - huge cost) - and fuck dealing mainly with CLI.
-
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
New to this purpose - yes... so I set it up with Hyper-V 2019 (yeah JB is spinning in his grave).
My old XenServer box needed to die - so I moved the VM to Hyper-V and killed it.
I didn't really care about XenServer/XCP-ng - so meh. I feel/felt I needed some hands on experience in Hyper-V, Plus I do have an AD environment, so I used Hyper-V. that's the long and the short. Ultimately I don't really give a shit which hypervisor I use. I might bail on it later.. I truly dislike the single pain of glass management of Hyper-V (at least without VMM - huge cost) - and fuck dealing mainly with CLI.
Thanks for explaining the reasoning!
Yeah so it sounds like you have some good reasons to use Hyper-V. But also some good reasons to not want to deal with it. I doubt that XCP-ng would be any easier or more difficult though.
Granted XO makes a lot of the operational things simple, but it's still important to know how the hypervisor works.
-
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
New to this purpose - yes... so I set it up with Hyper-V 2019 (yeah JB is spinning in his grave).
My old XenServer box needed to die - so I moved the VM to Hyper-V and killed it.
I didn't really care about XenServer/XCP-ng - so meh. I feel/felt I needed some hands on experience in Hyper-V, Plus I do have an AD environment, so I used Hyper-V. that's the long and the short. Ultimately I don't really give a shit which hypervisor I use. I might bail on it later.. I truly dislike the single pain of glass management of Hyper-V (at least without VMM - huge cost) - and fuck dealing mainly with CLI.
Thanks for explaining the reasoning!
Yeah so it sounds like you have some good reasons to use Hyper-V. But also some good reasons to not want to deal with it. I doubt that XCP-ng would be any easier or more difficult though.
Granted XO makes a lot of the operational things simple, but it's still important to know how the hypervisor works.
Oh - actually - I fully expect XCP-ng to be 100% easier. If it's not - I will never look at it beyond the first time. XenServer basically gave me exactly what I had in ESXi 5.5 - a locally installed app that allowed me to manage the hypervisor in a single pane of glass (was it called XenCenter?).
If XCP-ng doesn't do that - screw it.
I haven't dealt with KVM - but I feel the same about it.Yes we need the CLI options for those managing 10's or more of these things, but I don't.
-
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
I have AD and mostly Windows Servers - so Hyper-V is what I picked.
Those seem odd reasons. Lacking AD might make Hyper-V a negative, but having AD doesn't make it have any positive features. And Windows runs best on KVM, over Hyper-V. So normally, for what little the workload is worth, having Windows specifically would lead to KVM over Hyper-V.
That's all other things ignored, but the two factors that you mentioned are either "don't point to either" or "point to KVM".
-
It was mainly about - wanting to learn Hyper-V.
-
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
New to this purpose - yes... so I set it up with Hyper-V 2019 (yeah JB is spinning in his grave).
My old XenServer box needed to die - so I moved the VM to Hyper-V and killed it.
I didn't really care about XenServer/XCP-ng - so meh. I feel/felt I needed some hands on experience in Hyper-V, Plus I do have an AD environment, so I used Hyper-V. that's the long and the short. Ultimately I don't really give a shit which hypervisor I use. I might bail on it later.. I truly dislike the single pain of glass management of Hyper-V (at least without VMM - huge cost) - and fuck dealing mainly with CLI.
Thanks for explaining the reasoning!
Yeah so it sounds like you have some good reasons to use Hyper-V. But also some good reasons to not want to deal with it. I doubt that XCP-ng would be any easier or more difficult though.
Granted XO makes a lot of the operational things simple, but it's still important to know how the hypervisor works.
Oh - actually - I fully expect XCP-ng to be 100% easier. If it's not - I will never look at it beyond the first time. XenServer basically gave me exactly what I had in ESXi 5.5 - a locally installed app that allowed me to manage the hypervisor in a single pane of glass (was it called XenCenter?).
If XCP-ng doesn't do that - screw it.
I haven't dealt with KVM - but I feel the same about it.Yes we need the CLI options for those managing 10's or more of these things, but I don't.
So while XCP-ng has a Single Pane of Glass management and backup system, it is not a part of the hypervisor. You can't go to http://hypervisor-ip:8080 and manage it.
You need to install a VM first (either the appliance demo - which can be done via the CLI of the hypervisor) or Ubuntu and then setup XO by hand. (of course I'd recommend using the install script).
-
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
New to this purpose - yes... so I set it up with Hyper-V 2019 (yeah JB is spinning in his grave).
My old XenServer box needed to die - so I moved the VM to Hyper-V and killed it.
I didn't really care about XenServer/XCP-ng - so meh. I feel/felt I needed some hands on experience in Hyper-V, Plus I do have an AD environment, so I used Hyper-V. that's the long and the short. Ultimately I don't really give a shit which hypervisor I use. I might bail on it later.. I truly dislike the single pain of glass management of Hyper-V (at least without VMM - huge cost) - and fuck dealing mainly with CLI.
Thanks for explaining the reasoning!
Yeah so it sounds like you have some good reasons to use Hyper-V. But also some good reasons to not want to deal with it. I doubt that XCP-ng would be any easier or more difficult though.
Granted XO makes a lot of the operational things simple, but it's still important to know how the hypervisor works.
Oh - actually - I fully expect XCP-ng to be 100% easier. If it's not - I will never look at it beyond the first time. XenServer basically gave me exactly what I had in ESXi 5.5 - a locally installed app that allowed me to manage the hypervisor in a single pane of glass (was it called XenCenter?).
If XCP-ng doesn't do that - screw it.
I haven't dealt with KVM - but I feel the same about it.Yes we need the CLI options for those managing 10's or more of these things, but I don't.
So while XCP-ng has a Single Pane of Glass management and backup system, it is not a part of the hypervisor. You can't go to http://hypervisor-ip:8080 and manage it.
You need to install a VM first (either the appliance demo - which can be done via the CLI of the hypervisor) or Ubuntu and then setup XO by hand. (of course I'd recommend using the install script).
So there is no XenCenter like app for XCP-ng? - suck
-
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
New to this purpose - yes... so I set it up with Hyper-V 2019 (yeah JB is spinning in his grave).
My old XenServer box needed to die - so I moved the VM to Hyper-V and killed it.
I didn't really care about XenServer/XCP-ng - so meh. I feel/felt I needed some hands on experience in Hyper-V, Plus I do have an AD environment, so I used Hyper-V. that's the long and the short. Ultimately I don't really give a shit which hypervisor I use. I might bail on it later.. I truly dislike the single pain of glass management of Hyper-V (at least without VMM - huge cost) - and fuck dealing mainly with CLI.
Thanks for explaining the reasoning!
Yeah so it sounds like you have some good reasons to use Hyper-V. But also some good reasons to not want to deal with it. I doubt that XCP-ng would be any easier or more difficult though.
Granted XO makes a lot of the operational things simple, but it's still important to know how the hypervisor works.
Oh - actually - I fully expect XCP-ng to be 100% easier. If it's not - I will never look at it beyond the first time. XenServer basically gave me exactly what I had in ESXi 5.5 - a locally installed app that allowed me to manage the hypervisor in a single pane of glass (was it called XenCenter?).
If XCP-ng doesn't do that - screw it.
I haven't dealt with KVM - but I feel the same about it.Yes we need the CLI options for those managing 10's or more of these things, but I don't.
So while XCP-ng has a Single Pane of Glass management and backup system, it is not a part of the hypervisor. You can't go to http://hypervisor-ip:8080 and manage it.
You need to install a VM first (either the appliance demo - which can be done via the CLI of the hypervisor) or Ubuntu and then setup XO by hand. (of course I'd recommend using the install script).
So there is no XenCenter like app for XCP-ng? - suck
There is if you want a fat client (windows MSI client) called XCP-Center (https://github.com/xcp-ng/xenadmin/wiki) but that isn't the best approach to manage XCP-ng or XenServer.
It works, but is best for the rare occasion you only need console access.
-
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
New to this purpose - yes... so I set it up with Hyper-V 2019 (yeah JB is spinning in his grave).
My old XenServer box needed to die - so I moved the VM to Hyper-V and killed it.
I didn't really care about XenServer/XCP-ng - so meh. I feel/felt I needed some hands on experience in Hyper-V, Plus I do have an AD environment, so I used Hyper-V. that's the long and the short. Ultimately I don't really give a shit which hypervisor I use. I might bail on it later.. I truly dislike the single pain of glass management of Hyper-V (at least without VMM - huge cost) - and fuck dealing mainly with CLI.
Thanks for explaining the reasoning!
Yeah so it sounds like you have some good reasons to use Hyper-V. But also some good reasons to not want to deal with it. I doubt that XCP-ng would be any easier or more difficult though.
Granted XO makes a lot of the operational things simple, but it's still important to know how the hypervisor works.
Oh - actually - I fully expect XCP-ng to be 100% easier. If it's not - I will never look at it beyond the first time. XenServer basically gave me exactly what I had in ESXi 5.5 - a locally installed app that allowed me to manage the hypervisor in a single pane of glass (was it called XenCenter?).
If XCP-ng doesn't do that - screw it.
I haven't dealt with KVM - but I feel the same about it.Yes we need the CLI options for those managing 10's or more of these things, but I don't.
So while XCP-ng has a Single Pane of Glass management and backup system, it is not a part of the hypervisor. You can't go to http://hypervisor-ip:8080 and manage it.
You need to install a VM first (either the appliance demo - which can be done via the CLI of the hypervisor) or Ubuntu and then setup XO by hand. (of course I'd recommend using the install script).
So there is no XenCenter like app for XCP-ng? - suck
There is. It's basically a rebranded XenCenter. I forget what they called it, XCP something. (Not at home to look.)
-
Or for the "oh shit my XOCE installation is broken".
Which I should actually get back to figuring out the one-line installation process. I think it's a bandwidth issue as it should work. . .
-
@travisdh1 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@DustinB3403 said in Dashrender why did you migrate to Hyper-V from XenServer:
Ah so you already had a Hyper-V box, and just migrated your VMs and then reloaded the existing XS box with Hyper-V.
Fair enough.
well no - I decomm'ed the old box running XenServer.
Oh, that's completely different. So you have a new box, and just wanted Hyper-V?
New to this purpose - yes... so I set it up with Hyper-V 2019 (yeah JB is spinning in his grave).
My old XenServer box needed to die - so I moved the VM to Hyper-V and killed it.
I didn't really care about XenServer/XCP-ng - so meh. I feel/felt I needed some hands on experience in Hyper-V, Plus I do have an AD environment, so I used Hyper-V. that's the long and the short. Ultimately I don't really give a shit which hypervisor I use. I might bail on it later.. I truly dislike the single pain of glass management of Hyper-V (at least without VMM - huge cost) - and fuck dealing mainly with CLI.
Thanks for explaining the reasoning!
Yeah so it sounds like you have some good reasons to use Hyper-V. But also some good reasons to not want to deal with it. I doubt that XCP-ng would be any easier or more difficult though.
Granted XO makes a lot of the operational things simple, but it's still important to know how the hypervisor works.
Oh - actually - I fully expect XCP-ng to be 100% easier. If it's not - I will never look at it beyond the first time. XenServer basically gave me exactly what I had in ESXi 5.5 - a locally installed app that allowed me to manage the hypervisor in a single pane of glass (was it called XenCenter?).
If XCP-ng doesn't do that - screw it.
I haven't dealt with KVM - but I feel the same about it.Yes we need the CLI options for those managing 10's or more of these things, but I don't.
So while XCP-ng has a Single Pane of Glass management and backup system, it is not a part of the hypervisor. You can't go to http://hypervisor-ip:8080 and manage it.
You need to install a VM first (either the appliance demo - which can be done via the CLI of the hypervisor) or Ubuntu and then setup XO by hand. (of course I'd recommend using the install script).
So there is no XenCenter like app for XCP-ng? - suck
There is. It's basically a rebranded XenCenter. I forget what they called it, XCP something. (Not at home to look.)
It's called XCP-ng Center.
-
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
It was mainly about - wanting to learn Hyper-V.
Ah, that's totally different, and perfectly fine. But state that as the reason, not something else. If you had "no AD and only Linux workloads" it would actually make Hyper-V make more sense than it does here.
-
@scottalanmiller said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
It was mainly about - wanting to learn Hyper-V.
Ah, that's totally different, and perfectly fine. But state that as the reason, not something else. If you had "no AD and only Linux workloads" it would actually make Hyper-V make more sense than it does here.
I take it you have witnessed this or have read papers where people have shown that Hyper-V is better for linux workloads and KVM is better for Windows ones?
-
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
@scottalanmiller said in Dashrender why did you migrate to Hyper-V from XenServer:
@Dashrender said in Dashrender why did you migrate to Hyper-V from XenServer:
It was mainly about - wanting to learn Hyper-V.
Ah, that's totally different, and perfectly fine. But state that as the reason, not something else. If you had "no AD and only Linux workloads" it would actually make Hyper-V make more sense than it does here.
I take it you have witnessed this or have read papers where people have shown that Hyper-V is better for linux workloads and KVM is better for Windows ones?
They are about even for Linux, but KVM is the best for Windows. That's measured, yes.
-
The margins are small, but KVM has focused on Windows performance because Xen focused to have on Linux performance back in the day (because of Paravirtualization.)
-
So am I wrong for running both linux and windows workloads on hyper-v?
-
@murpheous said in Dashrender why did you migrate to Hyper-V from XenServer:
So am I wrong for running both linux and windows workloads on hyper-v?
Not at all. The hypervisor has very little effect on the guest performance. There are margins that you can stretch for if you need the absolute best possible performance for a specific workload. Which may sway your decision.
But you should choose your hypervisor based on the experience and familiarity with the tools you use regularly.
