131–140 of 162 posts
Earlier quoted context omitted.
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!
It's bad enough already, please no.
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…
Another ex-VMware here (9 years on the Workstation team). It's so very sad to see... I grew up there from a career standpoint and I was proud to be there, loved being there, and I just don't recognize it anymore. I agree with your point about "winning was the default state." I joined during the Diane Greene era and left in the Pat Gelsinger era, spoke to all three CEOs at different points in one-on-ones, and learned…
if you already pay for an ent backup product check if it can restore from vmware backups to another platform and you’re prolly fine (for now)
Earlier quoted context omitted.
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!
It's bad enough already, please no.
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 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? Microsoft hides their best stuff in SCVMM, which is another product and another license they want you to purchase. Anytime I've asked someone from MS why I can't X like I can in vCenter the response was usually, "oh, it's in System Center. FCM, HVM are ju…
But, hey, The Reg says that VMware is now claiming that vSphere Standard was never really cancelled.
https://www.theregister.com/virtualization/2026/09/02/vmware...
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…
I was a VMware workstation user in the late 90s.
I worked on the VMware monitor team back in 2007-2008, which probably put my employee number way in the 1000s. Ole Agesen, Carl Waldspurger, and other early folks were still there.
Back then "kvm" meant a remote keyboard/video/mouse device. Linux kvm was announced in 2006, and released in 2007, and required hardware virtualization, which was first released with AMD Pacifica in 2006. Back then VMware's binary translation was locked up in patents, so in the free software world we had Xen, colinux, and other hacks.
Earlier quoted context omitted.
Another ex-VMware here (9 years on the Workstation team). It's so very sad to see... I grew up there from a career standpoint and I was proud to be there, loved being there, and I just don't recognize it anymore. I agree with your point about "winning was the default state." I joined during the Diane Greene era and left in the Pat Gelsinger era, spoke to all three CEOs at different points in one-on-ones, and learned…
What do you think was the root cause?
Earlier quoted context omitted.
> 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 yea…
>A minuscule in modern times 1TB+ VM took a whole weekend to be moved Why?
And that was with the help of a backup-recovery solution which did support Proxmox, mere 6 months before that I would had stuck with an agent P2V migration of a VM to VM - which would had involved way more moving parts (can't P2V/V2V to a hypervisor which is not even installed yet) and more pain.
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.
So for all you can say, VMware released a product to market that provided a server-based hypervisor before any of their competitors. They're not the first hypervisor, but they're the first server-based hypervisor for X86.
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…
The problem is how you access the disks that are sitting on a VMware server. VDDK allows you to connect and read them (in raw format, in fact) at a reasonable speed, and also understands sparseness and change block tracking.