Date: Tue, 8 Sep 2020 12:50:00 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Mario Lobo <lobo@bsd.com.br> Cc: "freebsd-questions@freebsd.org" <questions@freebsd.org> Subject: Re: first use of virtualbox on fbsd host Message-ID: <CAN6yY1uLK-cOA-w37a2rkaDfbA%2Bo%2BLYyD30awW-45NeBHzamRA@mail.gmail.com> In-Reply-To: <CAN6yY1tXJ2=qiyTdSofYQcP%2BuECpX7s=ogTQdgd53TkjSveoSw@mail.gmail.com> References: <CAOjkAUdkK-vc=S1iBoE0KCQGhugcbifHTVyjpTAs-1wZvkMU5Q@mail.gmail.com> <CA%2ByoEx9OS7KX7KVdYaASWO-8b0t4-8BCMHFDFpdnwmvMCMFv=A@mail.gmail.com> <CAN6yY1vBG6BSSFowu9z7M3NqetHNJ7fzHAHSPKEpeSmwht1rdQ@mail.gmail.com> <CAN6yY1tXJ2=qiyTdSofYQcP%2BuECpX7s=ogTQdgd53TkjSveoSw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
You might also read "Controllimg VirtualBox from the Command Line" a nice "How-to" from Oracle. On Tue, Sep 8, 2020, 12:46 Kevin Oberman <rkoberman@gmail.com> wrote: > There are many sites with information on use of vboxmanage, but the first > I found is > https://www.techrepublic.com/article/how-to-import-and-export-vitualbox-appliances-from-the-command-line/ > > On Tue, Sep 8, 2020, 12:07 Kevin Oberman <rkoberman@gmail.com> wrote: > >> To cleanly move a VB VM to a new system, it's usually best to export it >> to an OVA, copy the .ova file to the new system, and import it. I Google >> and found a page with a nice set of commands to do it without a GUI, but my >> system is in transition to a new box and it will take a bit of hunting to >> find it. >> >> If I find it, I'll follow up. Or, maybe someone else will post it. >> >> On Tue, Sep 8, 2020, 11:56 Mario Lobo <lobo@bsd.com.br> wrote: >> >>> On Tue, Sep 8, 2020 at 3:50 PM S. Franks <bahamasfranks@gmail.com> >>> wrote: >>> >>> > Y'all, >>> > >>> > I've got some machines on my linux host I'd like to try on the fbsd >>> host. >>> > >>> > On linux, it's easy: copy the .vbox, and .vdi file to >>> > /home/$USER/.VirtualBox folder, run the gui, and it's right there in >>> the >>> > list. If not, manually edit the vbox file with a txt editor to fix the >>> path >>> > that's causing compliants. Edit vbox.xml file worst-case. Simple. >>> > >>> > I suppose I should mention the fbsd server is headless, which is >>> probably >>> > 9/10th's of the problem, since I can't run the control gui so it's >>> never >>> > created the deafult files? I searched the entire system, there's no >>> vbox >>> > xml file, probably cause I haven't ever successfully loaded a machine >>> on >>> > this system? There doesn't seem to be any vbox folders or files in >>> /etc, >>> > /usr/local/etc, /usr/share, etc. The handbook only tells you how to >>> install >>> > vbox, with zero info on making it run (so I guess it's supposed to >>> 'just >>> > work' for people who aren't idiots; sadly not a set which includes >>> myself >>> > apparently). >>> > >>> > I did convince some of the shell commands to error out with references >>> to >>> > /root/.config/virtualbox, but I can't seem to get the commands to >>> recognize >>> > the vbox and vdi files when I place them in that path either. Totally >>> > stumpped! >>> > >>> > Many thanks! >>> > _______________________________________________ >>> > freebsd-questions@freebsd.org mailing list >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> > To unsubscribe, send any mail to " >>> > freebsd-questions-unsubscribe@freebsd.org" >>> > >>> >>> >>> Even if it's headless, you can still run VirtualBox GUI through SSH with >>> x-forwarding. >>> -- >>> Mario Lobo >>> http://www.mallavoodoo.com.br >>> FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to " >>> freebsd-questions-unsubscribe@freebsd.org" >>> >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uLK-cOA-w37a2rkaDfbA%2Bo%2BLYyD30awW-45NeBHzamRA>