https://blogs.vmware.com/cloud-foundation/2024/11/11/vmware-fusion-and-workstation-are-now-free-for-all-users/
Interesting to see some good licensing news coming out of
VMWare/Broadcom, but concerned that they're doing this in advance of
them abandoning the desktop virtualization space.
Definitely. One year after taking it away from us, they're going to give it back. Why is them possibly taking it away /again/ at all concerning? I'd enjoy it while it lasts, if you wish to do so. If not to at least get a newe copy of something that will last you, free, for years. :)
yeah, I was a huge VMWare Workstation fan for years - even ran the BBS on it for some time. It might be too little, too late for me - I have Proxmox running in a homelab and VirtualBox running for a couple of desktop VMs.
https://blogs.vmware.com/cloud-foundation/2024/11/11/vmware-fusion-and-workstation-are-now-free-for-all-users/
Interesting to see some good licensing news coming out of
VMWare/Broadcom, but concerned that they're doing this in advance of
them abandoning the desktop virtualization space.
Having never used or seen VM Fusion or Workstation, I assume they're
similar to something like VirtualBox? If so, what is the advantage of
using them over said product?
Hello nelgin,
On Fri, Nov 22 2024 16:06:43 -0600, you wrote:
Having never used or seen VM Fusion or Workstation, I assume they're similar to something like VirtualBox? If so, what is the advantage
of using them over said product?
IMO, absolutely nothing. I originally got excited until I realized
they aren't anything like VMWare ESXi was.
For now, the best (new install) virtualization platforms to run on
bare metal are probably Proxmox, XCP-ng, and whatever that one is
called that you can build on a base BSD install - and in that order.
If you still have VMWare ESXi installed like I do, it works perfectly
fine still. :)
I don't have a hypervisor at home other then Virtualbox on my PC which
seems to do fine. I was thinking I'd play games and do more stuff on my
linux box than I do, but I still seem to use Winderz more. I'd consider
it except I don't have a huge amount of memory and I seem to use disk
space like it's going out of fashion. It's really easier just to spin
up a Virtoualbox VM.
nelgin wrote to All <=-
Having never used or seen VM Fusion or Workstation, I assume they're similar to something like VirtualBox? If so, what is the advantage of using them over said product?
Accession wrote to nelgin <=-
For now, the best (new install) virtualization platforms to run on bare metal are probably Proxmox, XCP-ng, and whatever that one is called
that you can build on a base BSD install - and in that order.
If you still have VMWare ESXi installed like I do, it works perfectly
fine still. :)
Yeah, I'm re-licensing ESXi/vSphere at work, not worth migrating
over to another platform. I'm tempted to look at XCP-ng, hear lots
of good things about it - but Proxmox just works!
I had problems getting VM Workstation running under Linux, it was too dependent on linux kernel versions - do an apt upgrade and VM
Workstation would break. Virtualbox didn't have that issue.
Accession wrote to poindexter FORTRAN <=-
I took a look at XCP-ng, and it's not bad at all. I actually like the
fact that it has a decent command line UI installed on the host machine
- aside from the web access most of these platforms offer. In
comparison to Proxmox though, you're losing out on containers.
sure how that would currently affect me just yet (I don't think it
really matters much, since I currently don't use them), but it seems at the moment there's much more community and helpful information out
there on Proxmox than there is XCP-ng.
That said, looks like Proxmox just came out with an update (8.3) that looks like they've added a few things.
Proxmox is just QVM/QEMU behind the GUI, and there are a decent
amount of commands available by SSHing into the box (and it's based
on Debian, so more commonality there)
The Proxmox helper scripts have quite a few homelab services
available to install as LXCs, and they take less resources than
setting up a docker host and running docker containers. Networking
is easier since you've got one IP address per container per app.
I really want to get 3 micro systems and set up ceph and zfs on it,
with proper HA - not that I need that at home, but it'd still be
neat to have.
[...]The Proxmox helper scripts have quite a few homelab services
available to install as LXCs, and they take less resources than
setting up a docker host and running docker containers. Networking
is easier since you've got one IP address per container per app.
So without the need of containers et al, maybe I could get away with either one. I'll have to do more studying up on which one is easier to update as well as migrate to and from.
One of the things that LXC's use is the server's own kernel.
Do you need a different kernel for your workload than what is in the
host? VM
Do you need live migration? VM
Do you need every ounce of performance and you are willing to
sacrifice some security? CT
Do you need a non-Linux OS such as Windows, FreeBSD or Hackintosh?
VM
A LXC container pretty much behaves as a TTY-only Linux VM. The
difference is that a LXC will share its kernel with the Proxmox host
and as such, any hardware-level vulnerability in the host will
expose the LXC CT and vice-versa.
Yeah, I'm re-licensing ESXi/vSphere at work, not worth migrating over to another platform. I'm tempted to look at XCP-ng, hear lots of good
things about it - but Proxmox just works!
maskreet wrote to poindexter FORTRAN <=-
https://pastebin.com/TGvtjsRe
Freakin' lifesaver.
jinkusu wrote to poindexter FORTRAN <=-
alternatives. there's another one i'm a little curious about called nutanix. it seems like it's growing in popularity, but have yet to actually speak to anyone using it.
One of the things that LXC's use is the server's own kernel.
Ah, I didn't know this part. I thought you install one VM (for
example, Debian) and then your containers ran on and around /that/
kernel. Not the actual kernel of the host (ie Proxmox).
A LXC container pretty much behaves as a TTY-only Linux VM. The
difference is that a LXC will share its kernel with the Proxmox host
and as such, any hardware-level vulnerability in the host will
expose the LXC CT and vice-versa.
The debate for me isn't really Proxmox vs XCP-ng, as they both would
be great for my use case. I guess I was looking at if I needed
containers or not, which I don't, and never have. Either or, both of
the above do VMs perfectly fine, Proxmox just offers containers,
whereas XCP-ng doesn't.
Thanks for the explanation, it definitely gave me some new information
I didn't already know!
Yeah, when I first started playing around with VM's (LXC's) via a
provider I quickly came to see the downside of them.. I think I
initially chose lxc due to the cost.. Then it was chalenge to get
some things working that I wanted (Ie: VPN).
Ever since that time, I've chosen real VM's and have been able to
treate each of them like they are real computers.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 91 |
Nodes: | 16 (0 / 16) |
Uptime: | 16:56:46 |
Calls: | 5,074 |
Calls today: | 6 |
Files: | 8,491 |
Messages: | 352,920 |
Posted today: | 1 |