beta ova file doesn't start in VirtualBox v5.2.44

[cannedit]

Hi,

I volunteered for testing the VRE, downloaded the beta ova file over here: https://ddhn.openpreservation.org/ddhn-beta.ova and tried to get that installed in my already existing VirtualBox v5.2.44 (with Extension pack), but it generates and error (attached). Is something wrong with this ova file or can it only be used in the latest version of VirtualBox, so v6.x?

[tledoux]

Hi, I volunter to.
I got the same error than you with my already installed Virtual Box 5.1.30.

Upgrading to the latest 6.1.16, makes the import successfull.

To be noted the installation of VirtualBox is fast, but the importation of the .ova takes about 30 minutes...

[cannedit]

Hi,

Ok, I switched to another computer (a Windows 7 system, the other one was a Windows 10 system), installed VirtualBox 6.1.16 and could now indeed install the beta ova file.

However, when trying to run it I got into trouble again: the system gave one error and two warnings, but I couldn't follow up on the suggestions to solve these because the options I had to change are all greyed out, so I got stuck again (see the screenshots attached).

Btw: the fact that the ova file can only be imported into a VirtualBox v6.x version should be in the manual; I know: officially the VirtualBox v5.x versions are not supported anymore, but a lot of people might still use these versions.

[cannedit]

Hi,

NDE was so kind to provide a new beta ova file (https://ddhn.openpreservation.org/ddhn-beta.ova) and I could make some progress using that, so I was able to change and save the setting of the second network adapter, but after the installation was finished I briefly saw the VRE screen passing by on my screen, but then I ended up with a Vagrant login screen:

[cannedit]

Hi,

I tried again, using the ddhn-rc.ova, and now it worked (and I didn't had to change the network adapters):

[carlwilson]

@cannedit thanks so much for your feedback, apologies for not being more proactive with replies. I can confirm that there were two issues, a misconfiguration of the virtual box extensions that only manifested itself intermittently and a rogue network adapter that was a by-product of the automated creation. I believe that they're both fixed in the RC and thanks for giving me cause for optimisim.

[carlwilson]

We believe this is fixed @cannedit and we will close this shortly unless we hear differently.