Live data from Hacker News

Leaving VMware just got harder after Broadcom pulled VDDK downloads

virtualizationhowto.com

11–20 of 161 posts

Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads

#11
post #8

Earlier quoted context omitted.

> […] could have been using Proxmox all along without any of the licensing and fee nightmares. As a user of Proxmox, and observer of VMware infrastructure in other silos in some IT orgs I've been in, there is no way that Proxmox was a viable solution 3-5 (or more) years ago. Hyper-V could have been used in many instances. I know a few places that chose to start moving to Nutanix even before the Broadcam fiasco. OpenS…

I was working on a pretty big proxmox setup back in 2016...

Well good news, it's improved quite a bit. File level restore is a thing now..

Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads

#12
post #9

I got my current job because I could lead the hyper-v to VMware migration project. Just this year I led the VMware to hyper-v migration project. VMware was such a great product (although a bit cumbersome in the VCF environment I managed). It’s really unfortunate it went the way of Broadcom. In comparison Hyper-v feels like a typical Microsoft product. A bunch of different tools created by different teams to do tasks…

I actually had so many troubles with vmware on windows over the years that once I tried out hyper-v for the first time last year, I somehow have never touched vmware again. Sure vmware has better configs, cleaner interface and some very subtle design advantages. But damn, hyper-v just fucking works and it keeps working across updates. I have a VM that has been running for a year and it is still perfectly doing exactly what it should. I never experienced that with vmware.

Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads

#13

Rather than converting the cold vm disk, couldn't you boot up the vm, dump the disks to stream, and send the streams into another format?

Probably better to get the vm into a ramfs or any other way to not be currently on it. Otherwise it'll likely be pretty corrupted

Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads

#16

Rather than converting the cold vm disk, couldn't you boot up the vm, dump the disks to stream, and send the streams into another format?

Yes, this is Microsoft's "agent-based migration" option mentioned in the article.

Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads

#17
post #9

I got my current job because I could lead the hyper-v to VMware migration project. Just this year I led the VMware to hyper-v migration project. VMware was such a great product (although a bit cumbersome in the VCF environment I managed). It’s really unfortunate it went the way of Broadcom. In comparison Hyper-v feels like a typical Microsoft product. A bunch of different tools created by different teams to do tasks…

I actually had so many troubles with vmware on windows over the years that once I tried out hyper-v for the first time last year, I somehow have never touched vmware again. Sure vmware has better configs, cleaner interface and some very subtle design advantages. But damn, hyper-v just fucking works and it keeps working across updates. I have a VM that has been running for a year and it is still perfectly doing exactl…

> I actually had so many troubles with vmware on windows...

I assume this means that you were using Vmware Workstation? The VDDK is for Vmware vSphere, which -IIRC- runs on Linux and coordinates computers running ESXi, which are where vSphere VMs actually run.

Not that many people are going to be using Vmware Workstation to run a large number of VMs.

Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads

#19
post #10

Earlier quoted context omitted.

> […] could have been using Proxmox all along without any of the licensing and fee nightmares. As a user of Proxmox, and observer of VMware infrastructure in other silos in some IT orgs I've been in, there is no way that Proxmox was a viable solution 3-5 (or more) years ago. Hyper-V could have been used in many instances. I know a few places that chose to start moving to Nutanix even before the Broadcam fiasco. OpenS…

I started migrating my customers from VMware a good three years ago. It does help that I have thirty years Linux experience compared to the paltry twenty five or so of VMware (which was RedHat plus stuff back in day) I also have rather a lot of Hyper V exposure too and I defy you to love its iSCSI and networking, let alone that awful vTPM thingie. It's Proxmox for me, any day. Even when I've completely knackered it I…

I too ran a large VDI, server, and scientific computing cluster based on Linux - libvirt in my case. I saved a bunch of money over VMware. When I quit to go to a higher paying job, they had to rip and replace everything with vSphere because they couldn't find anyone willing to work for .edu money with the skills to manage that despite the massive cost savings.

I had asked for vSphere to avoid this problem, and they balked at the licensing costs even in the good ol' days.

Post reply on HN