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.
Given my bad and costly experience with various commercial SW quality
and/or long term support, both personal and at work ---> I am of the
opinion that commercial software does not have positive ROI, fiscally and
intellectually - if there is a choice to be made. Most commercial solutions
look great on paper, if you can find what they are suppose to do at all,
but . Clearly commercial SW companies know it - hence the shift to
subscriptions, lobbying, competition removal, and various lock-in schemes.
My 2c - I would not touch VMware again, and vBox either, if not for legacy
reasons. KVM works and will keep working better.
-T
On Sat, Feb 12, 2022, 10:44 Chuck Hast wrote:
> 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 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 ... Windows 10.ovf
> > Detail
> > Result code NS_ERROR_INVAL ID_ARG (0x80070057)
> >
> > I tried it both ways - exporting as OVA and exporting as OVF, and the
> > new VirtualBox will try to import either one, but at the end always
> > gives the above error message.
> >
> > I also tried copying the Windows 10.vdi file to ~/VirtualBox/VDI on
> > the new computer (where I had to create the folder first), but the new
> > VirtualBox does not see the machine. I also tried putting it in
> > ~/VirtualBox VMs, which is the default folder that the installer
> > created on the new computer, but it still is not visible.
> >
> > At the end I decided to just reinstall Windows 10 in VirtualBox on the
> > new computer from the .ISO that I still have. It took a couple of hours
> > of swearing, but I finally got it installed, except when I launch it I
> > get a screen with a lot of little squares instead of a Windows 10
> > screen. In VirtualBox the icon for Windows 10 appears and the Settings
> > to the right also appear, and appear correct, but I can't figure out
> > how to fix the video problem.
> >
> > TomasK dijo:
> > >So, you need OVF to import it?
> > >Try export Virtual Appliance from menu then select one of the OVF
> > >formats.
> >
> > The format is not selectable, but (see above) the file that it will
> > create appears in a box below and you can just edit the name to .ova or
> > .ovf.
> >
> > >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 used
> > >to be.
> >
> > I don't understand the rsync commands above. The .vdi files are on one
> > computer and they need to be copied to a new computer, and the
> > computers are not directly connected. It is faster and easier just to
> > copy files from the old computer to a USB drive and plug the drive into
> > the new computer. And I already did that on the new computer, both to
> > ~/.VirtualBox/VDI (which I had to create) and to ~/VirtualBox VMs
> > (created by the installer of 6.1.26).
> >
> > Tomorrow I'm going to scour the VitualBox forums hoping to find step by
> > step 'for dummies' instructions for how to install Windows 10 from an
> > ISO.
> >
> > I should add that this is not a crucial matter. My old computer has
> > Windows 2000, Windows XP and Windows 10, and none of them have been
> > run for at least a couple of years; Windows 2000 for at least five
> > years. If I had any brains I'd just forget about it.
> >
> > I should add that the old computer has Xubuntu 20.04.2 with VirtualBox
> > 6.1.16 and the new computer has Xubuntu 21.10 with VirtualBox 6.1.26.
> >
>
>
> --
>
> Chuck Hast -- KP4DJT --
> I can do all things through Christ which strengtheneth me.
> Ph 4:13 KJV
> Todo lo puedo en Cristo que me fortalece.
> Fil 4:13 RVR1960
>
