I have finally succeeded. It took seven hours to get it working. During
that time I also installed KVM, which I had never heard of before, and
tried to install Windows 10 Pro 64-bit, using the same install media
(ISO file) that I had used to install it on VirtualBox several years
ago. I had also tr
I have no intention to judge other people choices - just my opinion + this
is pLUG.
No usb issues with Virtual Box here for about decade now - using Oracle
repo + virtualBox Additions.
I have no issues using usb with KVM either. I feel KVM is better and more
performant than VirtualBox these days.
VirtualBox USB issues drove me to VMWare, and
since for personal use it is free, I started using it.
Never had any issues moving a VM from one
VMWare machine to another. I never tried VB
again due to the USB issues I encountered.
On Fri, Feb 11, 2022 at 11:21 PM John Jason Jordan wrote:
> I di
I discovered that I can export from the old VirtualBox to OVF format
just by manually changing the name of the file it will create from .OVA
to .OVF. And the new VirtualBox on the Latitude will import it, except
that at the end the import fails:
VirtualBox Error
Failed to import appliance ... Wind
So, you need OVF to import it?
Try export Virtual Appliance from menu then select one of the OVF
formats.
I do not bother - just:
rsync -a "VirtualBox VMs" .../home/$USER/
rsync -a .config/VirtualBox .../home/$USER/.config/
Then start your new virtualbox and you should see everything as it us
I have had VirtualBox on my Lenovo laptop and its predecessors for many
years, and it always just works. Now that I have a new computer I
decided to install it there also, and copy the VDI file for Windows 10
over there also (I have multiple licenses). In the past this always
worked when I needed t
