Date: Mon, 10 Dec 2012 17:34:25 +0200 From: Alexander Yerenkow <yerenkow@gmail.com> To: Perry Hutchison <perryh@pluto.rain.com> Cc: freebsd-hackers@freebsd.org, zbeeble@gmail.com, aryeh.friedman@gmail.com Subject: Re: using FreeBSD to create a completely new OS Message-ID: <CAPJF9w=FQBU%2ByYB9Acy%2BBiPYY1scdJ0rVhRN9T2AR3uHwgeORg@mail.gmail.com> In-Reply-To: <11212101048.AA17688@pluto.rain.com> References: <11212101048.AA17688@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If you consider VirtualBox for automated tests, you should make some testing life cycle. I'd recommend to you: 1. create sparse file (truncate -s 1G for example) 2. mdconfig -af file (produced md0) 3. work with md0 as if it was real hw disk (write boot sectors, fs, etc), then destroy md0 (mdconfig -du 0) 4. create vmdk for file ( https://github.com/yerenkow/freebsd-vm-image/blob/master/freebsd-firmware/create-scsi-vmdk.sh -- this helps me create vmdk for raw file and feed them to VmWare/Virtualbox just fine) 5. boot VirtualBox using cli (and run some tests). I had some experience in running in-virtualbox-os tests a while ago, but there was real OS there, and not test one. Hope this helps. -- Regards, Alexander Yerenkow
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPJF9w=FQBU%2ByYB9Acy%2BBiPYY1scdJ0rVhRN9T2AR3uHwgeORg>