Migration from vSphere to Hyper-V

[-]

slugshead@reddit

I do miss having a web page to manage everything from. WAC just isn't the same.

vSphere VMs boot a LOT faster than Hyper-v guests

[-]

LesPaulAce@reddit

Take a look at Azure Local (formerly known as Azure Stack HCI). It might have some value to you.

[-]

RiceeeChrispies@reddit

friends don’t let friends use azure local

[-]

nervaickarma@reddit

tbh - our experience with azure local has been fantastic. I know that's a bit against the grain, but it's been great.

[-]

LesPaulAce@reddit

Now that you mention it.... I take back my advice and side with you, u/RiceeeChrispies .
Azure Local is not a go-to thing except for some very specific use cases.

[-]

EnDR91-EC@reddit

You mean WAC or WAC virtualization mode? The WAC vmode is nice

[-]

_litz@reddit

You should be able to use the same fiber connect storage you had with vSphere in Hyper-V ... not sure why'd you switch to iSCSI. IBM FlashSystems should be able to both, or either, method.

If you want to get super fancy with UCSX, and M8 blades, you can even do NVME over iSCSI.

[-]

ConstructionSafe2814@reddit

Sorry can't directly comment on you Hyper-V question because I have no experience. Have you considered Proxmox though? Or a reason why you choose Hyper-V over Proxmox?

[-]

To manage Proxmox, you need to be a skilled Linux administrator - and that has a lot of needed supporting skill-sets. So, you should be able to roll your own Bash scripts, be comfortable debugging someone else's script in an arbitrary which could include anything from Python to Bash to Perl, be able to write a Puppet or automation job, etc...

What I am saying is that there is a long-tail of skills that the average virtualization team at most companies will not have; if they do, it is likely a small-subset of the team. Yes, there is a ton of industry Linux virtualization experience- but it is heavily siloed in the tech sector. Outside of tech, it is heavily Windows on VMWare and has been for 20+ years. A large company will have a Linux team - but they are not doing virtualization administration. They are DevOps, developers, scripters, and direct revenue generation. And the type of people doing that work would not be interested in transferring to a virtualization support team. Essentially, going from VMWare to Proxmox does not have a ton of transferable skills. The same teams doing the migration will need to support it so they choose a platform they can support.

[-]

checkpoint404@reddit

Because Hyper-V is enterprise and supported by hardware vendors. Proxmox is not and you will not get any support from vendors

[-]

flecom@reddit

I mean, when we started deploying vmware ages ago there was no support from vendors either....

[-]

checkpoint404@reddit

You can't compare VMware to proxmox....regardless of Brodcom shit there is no comparison between the two products. VMware is still the best in the business in terms of a hypervisor platform.

[-]

Former-Mountain-9170@reddit (OP)

We are playing with Proxmox. But we have found that there is no official support from HW vendors like Cisco or IBM. Also many virtual appliances have no support from their vendors. I know that if I tried to get support for e.g. our production Cisco ISE that the immediate response would be: "This configuration is not supported."

[-]

homing-duck@reddit

That was one of the main reasons for us to go hyper-v. Last week I was looking at deploying a Cloudflare (I think) virtual appliance. Only available in VMware and proxmox… sigh… times are changing.

[-]

redstarduggan@reddit

Have looked at proxmox but we use some virtual appliances that are vmware, hyperv, nutanix and/or cloud native. It's hyperv or pay vmware for us, so will be hyperv.

[-]

flecom@reddit

When we were using hyperv we used iSCSI and it worked fine... Finally moved to proxmox though

[-]

homing-duck@reddit

We just finished. Pain points for us:

-No USB pass through

-Clunky management tools (can live with it, but much preferred VMware)

-No rbac

-no storage snaptshot explorer in veeam

-no CDP in veeam

-oh my god, the reboots. When we were initially testing, it seemed like we needed to reboot windows like 5-6 times to get to a point where we could start using the server. And with 768gb of ram, reboots were like 10+ minutes. Install drivers reboot. Update firmware Reboot. Join domain. Reboot. Install failover cluster. Reboot. Install iscsi initiator, and multipathing. Reboot. Install nimble storage tools. Reboot

[-]

derfmcdoogal@reddit

I think you can do USB pass through with an enhanced session which is basically rdp.

[-]

homing-duck@reddit

Needed to pass usb ports from the host, not a client connecting to a vm.

We have some vm’s that need usb dongles for licensing. The usb needs to be connected to the vm 24x7. Not just when someone is connecting to the vm.

[-]

ensum@reddit

You can do DDA but it requires passing through a whole PCI device. I have it setup with a dedicated USB card on one of my hosts for this purpose. Doesn't really scale well but can be used in a pinch.

[-]

MrMrRubic@reddit

There exists some USBoIP devices for that purpose, and IMO is better than regular passthrough for licencing because you're not having to bind a VM to a host.

[-]

Lando_uk@reddit

I'm curious about the same thing. I'm also wondering if you need to buy Microsoft Unified support if you have prod clusters, or are most issues easy to sort out, unlike vmware where i feel paid support is essential.

[-]

PMURITSPEND@reddit

You should look into unified support from a partner of your choosing and not Microsoft. Microsoft already went through the process of "optimizing for efficiency" in that group and fired 90% of the people with brains, overwhelming the remaining 10% and replaced them with people asking for logs you already sent.

[-]

sysacc@reddit

One of the reasons I like VMware is that I never had to call support. Paid for it, but never needed it.

[-]

Former-Mountain-9170@reddit (OP)

I only called VMware support once in 19 years. I turned off VSAN cluster because of bad GUI wording.

[-]

homing-duck@reddit

I doubt it. Pretty sure Unified support is just someone forwarding your request to copilot these days

[-]

dflek@reddit

We migrated. I do miss vSphere, especially when configuring new clusters. vSphere networking and shared storage setup is far superior IMO. HyperV works, but the interface and management tools are nowhere near as capable for me. Once it's all set up, it's fine though.