logoalt Hacker News

Leaving VMware just got harder after Broadcom pulled VDDK downloads

79 pointsby josephcsibleyesterday at 8:32 PM36 commentsview on HN

Comments

soamvtoday at 12:47 AM

As an old ex-vmware eng it's kinda sad reading all these articles about broadcom's controlled descent into terrain. A lot of really cool and useful engineering was done in vmware's heyday, and it was often delivered in rather shaky commercial shapes, but for a while the whole thing kinda worked. And broadcom seems to see it as a company that is long past its ability to innovate, extracting as many dollars as possible before its rapidly decreasing value goes to zero.

There was a solid few years that a lot of business types at vmware behaved as though winning was the default, assured state. It took several years for them to see that that was very much not the case. A real lesson in there, for every successful business today.

show 1 reply
ramgineyesterday at 11:01 PM

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 that feel bolted on and afterthoughts. I have to run FCM to manage the nodes? But I run HVM to manage the roles? But there’s no overall resource management like VMware vsphere or proxmox does natively?

I’ve quietly built a proxmox cluster in our environment for semi-prod workloads for when the inevitable windows host has issues.

show 1 reply
Jeddyesterday at 10:48 PM

From TFA

> VMware to Proxmox migrations are not affected ...

Amusingly - and acknowledging tiny scale and modest automation requirements of home lab compared to enterprise - as I started migrating to Proxmox a year or two ago, the process of shuffling VMs off my ESXi servers and onto Proxmox was surprisingly painless. Effectively mount the ESXi as storage systems, and then 'copy to here'.

IIRC the only small challenges were a conservative choice on target VM's CPU type (Proxmox seems to dislike defaulting to 'host' CPU) and the network / SCSI controller defaults. I assume designed to prioritise robustness over performance.

All automatable, I'm sure.

dare944today at 12:04 AM

> I am of the school of thought that even if Broadcom gives VMware Standard away free for a year, it would be hard to convince customers that they need to stick with the platform

Yep. They're building the cage around you. Why would you stick around?

firesteelrainyesterday at 11:41 PM

We run a lot of ESXi with vSphere (part of overall VCF solution). It works very well. But I am part of Big Corp. so they don’t mind paying. We are good via warranties etc using what we already purchased. I don’t know that I share the same sentiment that we could have just used ProxMox. We are a Dell heavy shop and there is a new Dell Private Cloud product that is very promising. More like choose your own adventure.

nubinetworkyesterday at 10:55 PM

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?

show 2 replies
uriahlightyesterday at 10:12 PM

The sad part is that most companies using VMWare could have been using Proxmox all along without any of the licensing and fee nightmares.

show 1 reply
jijjitoday at 12:52 AM

i thought everyone got rid of vmware in 2007 when virtualbox came out... wow cant believe people still pay for that

show 1 reply
akulbeyesterday at 10:54 PM

More VMware - winning friends and influencing people, like usual.

show 1 reply
toomuchtodoyesterday at 8:40 PM

Is a magnet torrent available?

show 1 reply
msieyesterday at 11:22 PM

Time to sue!

show 1 reply