On Tue, 2010-03-16 at 11:30 -0500, Dustin Kirkland wrote: > On Tue, Mar 16, 2010 at 11:10 AM, C de-Avillez <hgg...@ubuntu.com> wrote: > > I have been using testdrive [1] as a tool for running ad-hoc ISO tests. > > I like it -- it simplifies my life, not having to worry about syntax on > > qemu-img and qemu/kvm. Heartly thanks go to Dustin, for having made my > > life easier :-) > > Cheers, mate ;-) > ... > > This absolutely breaks when the user wants to run VirtualBox -- > > the VirtualBox definitions are hard-coded in testdrive, so there is no > > way a no-network test run can be done without code changing by the user. > > > > So we should look at changing the way these parameters are passed, so > > that both KVM and VirtualBox can profit from one single set of > > parameters. > > Right, so Testdrive started out as being a KVM-specific way of testing > the daily Ubuntu ISO's. But only half of the hardware out there can > run KVM. So VirtualBox was bolted on after the fact. > > Generally speaking KVM and VirtualBox support similar features. > Really, I just don't know how to "get at VirtualBox" from a command > line. For starters, I think you could just use some VB expertise and > get them to help hack Testdrive.
The VB user manual [1] details everything you need to know. You probably want section 8 on VBoxManage. I'm happy to help hack / test / debug the VirtualBox options if that can help, although I'm no expert. [1] http://www.virtualbox.org/manual/UserManual.html Bruno -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
