Fails to completely create VM in VirtualBox 3.1

Bug #495178 reported by Paul Rudkin
40
This bug affects 5 people
Affects Status Importance Assigned to Milestone
TestDrive
Fix Released
Medium
Paul Rudkin
testdrive (Ubuntu)
Fix Released
Medium
Dustin Kirkland 

Bug Description

I have just installed TestDrive on Karmic AMD64, and the script says I must use VirtualBox on my system, however after downloading the ISO of Lucid TestDrive fails to completely create the VM in Virtualbox. The output from my session is attached.

I am not sure if it is relevant but I do not store my VirtualBox VMs in the default location.

Revision history for this message
Paul Rudkin (paulgit) wrote :
Revision history for this message
Jean Levasseur (levasseur.jean) wrote :

I confirm this bug. Exact same error message on same architecture (Amd64). However, reverting to virtualbox-3.0.12 corrects the problem. It would be nice to make it work as well with the newer virtualbox, since there is lots of bugfixes/new features!

Changed in testdrive:
status: New → Confirmed
Revision history for this message
Paul Rudkin (paulgit) wrote :

I will try reverting, as long as my other VMs still work!

The fix should be easy. I cannot find the source for Testdrive anywhere else I would have a got at fixing it myself!

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Testdrive is a shell script. If you want to look at the source code, simple open /usr/bin/testdrive in your favorite editor. Send a patch.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

My apologies, I know very, very little about virtualbox, so any advice on fixing this would be appreciated. I developed and test this against virtualbox-ose 3.0.8-dfsg-1ubuntu1, where it works pretty well.

Changed in testdrive:
importance: Undecided → Low
Revision history for this message
Paul Rudkin (paulgit) wrote :

I have had a brief look into this and some of the command line parameters for VBoxManage have changed a bit in v3.1 of VirtualBox. I have a version of the script working but I would like to get it auto detecting the version of VirtualBox and making the relevant calls. A couple of other improvements can be made such as specifying the video card ram etc.

Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: [Bug 495178] Re: Fails to completely create VM in VirtualBox 3.1

Sweet, thanks.

I'll await your patch or merge proposal ;-)

Revision history for this message
Paul Rudkin (paulgit) wrote :

Here is a patch for TestDrive to work with VirtualBox 3.1. I have tried it with i386 guests and a AMD64 guest (though my hardward does not support 64bit guests) and the process of creating/deleting the virtual machine works.

I have yet to revert back to 3.0.x of VirtualBox to see if all still works, I am hoping somebody using 3.0.x can verify this independently.

I have attached a patch (created via diff, not sure if this is the best way to submit patch??)

Paul Rudkin (paulgit)
Changed in testdrive:
assignee: nobody → Paul Rudkin (rudders)
status: Confirmed → In Progress
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Paul-

Thanks so much for the patch.

I made a few modifications to it, when applying it. I wanted to reduce the amount of virtualbox duplicated code as much as possible. Seems that the two share a fair amount. I used case statements to handle the places where it's different.

I tested here with Karmic's virtualbox 3.0.*, and it still works. Could you test with 3.1.* and let me know if that works too? Attach another patch if I bungled up your changes such that 3.1 is broken.

Thanks!

Changed in testdrive:
status: In Progress → Fix Committed
Changed in testdrive (Ubuntu):
assignee: nobody → Dustin Kirkland (kirkland)
importance: Undecided → Medium
status: New → Fix Committed
Changed in testdrive:
importance: Low → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package testdrive - 1.16-0ubuntu1

---------------
testdrive (1.16-0ubuntu1) lucid; urgency=low

  * testdrive, testdrive-select-iso: separate the img and iso in the
    cache directory
  * doc/testdrive.1, testdrive: respect xdg, LP: #501766
  * debian/control: depend on virtualbox >= 3.0.8 (Karmic), which currently
    seems to be the oldest successfully tested version of virtualbox to
    work with testdrive, LP: #499413
  * testdrive-select-iso: if the user doesn't have VT, then defaul to
    i386 images, LP: #497984
  * testdrive, testdrive.desktop: make sure error messages get shown to
    the user, if running from the desktop menu, LP: #497955

  [ Paul Rudkin and Dustin Kirkland ]
  * testdrive: support virtualbox 3.1, LP: #495178
 -- Dustin Kirkland <email address hidden> Sun, 13 Dec 2009 22:51:23 -0600

Changed in testdrive (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Paul Rudkin (paulgit) wrote :

Dustin,

I was in two minds about not duplicating the code, but was concerned it could get messy if we were to support multiple version of VirtualBox, but now the minimum requirement is 3.0.8OSE I think the case statement solution is best.

I have just tested the script you committed and it still works fine with VB 3.1.

Paul

Changed in testdrive:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.