it seems that the vmdk format is too new for virtualbox and kvm .
here is the virtualbox output :
Failed to open the hard disk C:\Users\mike\Documents\My Virtual Machines\navtest\nav-lenny-appliance-disk1.vmdk. Could not get the storage format of the medium 'C:\Users\mike\Documents\My Virtual Machines\navtest\nav-lenny-appliance-disk1.vmdk' (VERR_NOT_SUPPORTED). Result Code: VBOX_E_IPRT_ERROR (0x80BB0005) Component: Medium Interface: IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd} Callee: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}
i'll try to get a vmware copy to run it
thanks
"Morten Brekkevold" morten.brekkevold@uninett.no a écrit dans le message de news:yylobrsiz9u.fsf@voldsminde.uninett.no...
On Sat, 17 Mar 2012 22:03:10 +0100 "dilbert" penne296@sapo.pt wrote:
I tried to use the nav ( lenny ) virual appliance with virtualbox ( by importing the ovf ) but it failed. vitrualbox complained that the vmdk was incorrect.
i downloaded it again on another computer and tried to convert the vmdk with qemu-image but it also complained that the vmdk was incorrect.
could you confirm that the latest vmdk uploaded on your server really works ?
Actually, it seems I can't even get my copy of VirtualBox to import any appliances at all at the moment. When I click the "choose" button, the VirtualBox application just crashes and disappears.
The NAV/Debian OVF image was exported from VMWare ESXi, and I've had multiple issues with exchanging OVFs between VirtualBox and VMWare before, so it wouldn't exactly surprise me that you are having problems.
Did you verify the SHA1-sums of the image after downloading?
The image has been the same the last 12 months, this complaint is the first I've heard. Has anyone on this list downloaded the appliance and tested it successfully within the last 12 months?
-- Morten Brekkevold UNINETT