Live data from Hacker News

Leaving VMware just got harder after Broadcom pulled VDDK downloads

virtualizationhowto.com

91–100 of 161 posts

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

#91

Most of VMware virtualization code was stolen from kvm and they never were punished. Our laws are a joke, our courts are largely illegitimate and so to is our government.

You are hallucinating and don't have any clue what you are talking about (VMware employee #10/11 -- I lost count, First Director of PM at VMware).

VMwware sure as hell did not invent the hypervisor, and we were damn careful not to ever claim that. The early unique IP was how to enable a hypervisor to use dynamic translation where required to work around non-virtualizable x86 instructions, we also did well with how to package a hypervisor to run on a host/share host devices etc. Over time that early differentiation went away as we helped encourage CPU vendors to include better hardware virtualization support. And the other big thing we had was just a market focus/desire to deliver value/delight nerdy users like ourselves.

Who is the granddaddy of hypervisors? It sure ain't KVM, and it sure ain't VMware. That would be IBM. They had decades of doing hypervisors on the mainframe when we were getting started as a tiny startup. They sure know a lot about hypervisors and had a x86 hypervisor research project in Watson labs. We were humbled when IBM fellow Rich Oehler came to us wanting to partner because he saw how far ahead we were. That was years before KVM even got started. The IBM collaboration, lead to years of great work with IBM, who helped VMwware get going with ESX Server. Although the focus of VMware since founding was always to end up focusing on the data center/server market we could not have done that so well and so fast without IBM and sales and GTM cooperation.

Now good on KVM and others for pushing open hypervisor technology, and any company in this space who actually cares about their users and customers. I hope KVM helps pound VMware/Broadcom into the dirt.

Edit: typos

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

#93
post #82

Earlier quoted context omitted.

You need to remember this isn't Broadcom the chip company at work, this is really Avago which took on the Broadcom name when they acquired the latter. Avago's business model is to acquire cash cow businesses and then milk them dry. These VMware changes are consistent with that model.

Broadcom/Avago, please buy Atlassian! I beg you, pretty please! You will make an insane amount of money and make the world a much better place!

Or the equivalent of "Superstorm Sandy" is created...

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

#94

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.

Agent based requires an insane amount of privileged accounts and I would say fails for 10%+ of the VM population

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

#95

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

Proxmox is good for a home lab but running an enterprise on it is a joke. Good luck with that

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

#96

So the Linux qemu-img tool can still convert VM disk images from .vmdk into formats compatible with all the other hypervisors. Is there something more to the process of VM migration from VMWare than just using this tool (and manually creating the proper virtual hardware profile in the new hypervisor)? Obviously the types of supported virtual hardware will be different between hypervisor types, but that's usually some…

> Is there something more to the process of VM migration from VMWare than just using this tool (and manually creating the proper virtual hardware profile in the new hypervisor)?

Yes? Do that for the hundreds of VMs, with a minimal downtime, bonus points for a dumb C-level on your neck.

You would quickly learn what "just converting disk images" is not enough for moving between hypervisors.

Just as an example: last year I moved a company with two Proxmox servers to ESXi. It took a 3 months and another server as a staging point. A minuscule in modern times 1TB+ VM took a whole weekend to be moved. Of course it didn't work in that time.

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

#97
post #87

Leaving VMware just got harder? What? NO! It just became more obvious that you've failed if you are still stuck there. (VMware employee #10/11 -- I lost count. First Director of PM).

And I know that sounds like victim blaming. Anybody stuck in this situation has my empathy. But I just don't know how to get it across to some company execs/leaders that they have been needing to get their act together and get off VMware for coming on near 3 years now.

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

#98
post #56

Earlier quoted context omitted.

Does your company have a ton of thick-client apps? I feel like so many workloads are on the web right now and thick clients are slowly becoming a thing of the past - but maybe in Enterprise there are still stubborn thick client Win32 apps that are mission critical. If I were starting a company today I would make sure that the majority of my apps were web based. (CRM[netsuite or sf.com], O365/GoogleDocs, workday|gusto…

Most high-security environments (banks, govt agencies etc) have a large on-prem footprint. Then there's specialised industries like manufacturing, science and engineering who typically have a bunch of embedded systems, often running ancient versions of Windows or something that needs to talk to a local ancient server. And many old companies have tons of legacy apps which are a PITA to migrate to newer infrastructure.…

Reminds me of setting up VMware Workstation with USB ISA cards to keep a line running. Ugh

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

#99

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

Proxmox is good for a home lab but running an enterprise on it is a joke. Good luck with that

You work for Broadcom don't you fella?

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

#100

Earlier quoted context omitted.

> quietly built a proxmox cluster Why is your place of work not moving wholesale to Proxmox? It's mad that HyperV is chosen as a solution in this day and age.

Proxmox is amateur hour. No enterprise support

> Proxmox is amateur hour. No enterprise support

24/7 support will be available starting in October:

* https://www.proxmox.com/en/about/company-details/press-relea...

The other thing perhaps worth noting that the entire stack is open source, even Proxmox's 'special sauce' for management. Depending on your organization, if you can solve a problem with Debian (and Qemu) you can solve a problem with Proxmox.

Post reply on HN