Well If you dig through the proxmox documentation you can migrate Debian over to Proxmox or even set up Xwindows on proxmox so you can have a UX on top of the proxmox environment.
This may suit your needs a bit.
Thanks Arun,
Your last sentence is where I am at "The bottom line -- both VB and
Proxmox (KVM) are very powerful, you
need to figure out your use case and pick the appropriate platform.".
I hope to upgrade my desktop and network in 2026...
I currently run Kubuntu on an old Dell with an i5 w/ 4 cores and 4
threads. It has 16G of RAM... just barely enough. Good enough for my
needs. I am running an old HP laptop that is WIN10 running VirtualBox
for development and testing. I run it because it runs my Win only video
software. I have a Proxmox server on an old dell as well. I have not
use the Proxmox for a while....
There is a person on the list that does everything on his laptop. That
is a consideration. I do need a NAS as well. Nothing too extravagant.
I need a decent backup and something for file sharing.
Keith
On 2025-01-12 11:19, Arun Khan wrote:
> On Sun, Jan 12, 2025 at 9:38 AM Keith Smith via PLUG-discuss
> <plug-discuss@lists.phxlinux.org> wrote:
>
>> Hi,
>>
>> Anyone using KVM (Kernel-based Virtual Machine) ?
>
> Yes, I have deployed KVM VMs since c. 2009 (initially wrote bash
> scripts for each VM); used virt-manager and virsh later on. And now I
> plan to use Proxmox VE for KVM VMs.
>
>> How does it compare to VirtualBox and/or Proxmox?
>
> VirtualBox v/s KVM -- IMO, they are an apple and an orange. VB is a
> desktop app with its own network and storage drivers that load as
> kernel modules plus it provides sound and USB support. VB can leverage
> hardware acceleration (KVM). Whereas, KVM is Linux kernel native and
> more appropriate for a server setup. I use VB a lot to evaluate
> software, test use cases, and then migrate the VM to KVM server for
> production usage. You can also launch VB VMs (headless) for server
> apps on your desktop, make sure the VM NIC is bridged to the desktop
> NIC/WiFi and is configured as a DHCP client. On the DHCP server, you
> can program the VM's NIC MAC address to a fixed IP address. (see
> 'vboxmanage help' for a synopsis of the possibilities)
>
> VB v/s ProxmoxVE (see above). Proxmox (Debian-based) is essentially
> KVM with a very functional and easy-to-use Web UI.
> IMO, it is n00b friendly and can be set up on a repurposed thin client
> (8GB RAM/128 GB storage) or as a VB VM*; a quick and easy way to get
> your hands wet with the product. It is well documented and the user
> forum is very helpful.
>
> * Here is the power of both tools -- Most modern CPUs support *nested*
> virtualization; you need to turn it ON (Google it).
> I evaluated Proxmox VE as a VB VM and spun up a couple of small VMs
> within the Proxmov VE 🖖
>
> The bottom line -- both VB and Proxmox (KVM) are very powerful, you
> need to figure out your use case and pick the appropriate platform.
>
> HTH
> --
> Arun
---------------------------------------------------
PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
--
A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button.
Stephen