Docker Community Forums

Share and learn in the Docker community.

Import an vmdk in new virtualBox on windows10

Hi
I have reinnstall docker CE in my computer, new installation is running, but when i tried to add old vmdk with all my datas, i have following error message

Regards

In docker terminal

too many retries waiting for SSH to be available

In vbox.log
00:00:32.490850 NAT: IPv6 not supported
00:00:34.850246 VMMDev: Guest Log: VBoxService 5.2.34 r133893 (verbosity: 0) linux.amd64 (Oct 10 2019 20:19:38) release log
00:00:34.850275 VMMDev: Guest Log: 00:00:00.000056 main Log opened 2020-03-14T17:16:54.153432000Z
00:00:34.850855 VMMDev: Guest Log: 00:00:00.000675 main OS Product: Linux
00:00:34.851243 VMMDev: Guest Log: 00:00:00.001063 main OS Release: 4.14.154-boot2docker
00:00:34.851504 VMMDev: Guest Log: 00:00:00.001326 main OS Version: #1 SMP Thu Nov 14 19:19:08 UTC 2019
00:00:34.852145 VMMDev: Guest Log: 00:00:00.001964 main Executable: /sbin/VBoxService
00:00:34.852159 VMMDev: Guest Log: 00:00:00.001965 main Process ID: 2073
00:00:34.852165 VMMDev: Guest Log: 00:00:00.001966 main Package type: LINUX_64BITS_GENERIC
00:00:34.854718 VMMDev: Guest Log: 00:00:00.004543 main 5.2.34 r133893 started. Verbose level = 0
00:00:34.857874 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x1, 0x8000000000000000
00:00:34.861110 VMMDev: Guest Log: 00:00:00.010903 vminfo rtldrNativeLoad: dlopen(‘libdbus-1.so.3’, RTLD_NOW | RTLD_LOCAL) failed: libdbus-1.so.3: cannot open shared object file: No such file or directory
00:00:34.861321 VMMDev: Guest Log: 00:00:00.011137 vminfo Error: Unable to connect to system D-Bus (1/3): D-Bus not installed
00:00:34.865794 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:39.866457 VMMDev: Guest Log: 00:00:05.014276 vminfo Error: Unable to connect to system D-Bus (2/3): D-Bus not installed
00:00:44.870179 VMMDev: Guest Log: 00:00:10.015509 vminfo Error: Unable to connect to system D-Bus (3/3): D-Bus not installed

In vboxhardening.log
10a0.4ec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff977280000 ‘C:\WINDOWS\System32\winmm.dll’
10a0.3b48: ‘\Device\HarddiskVolume1\Windows\System32\tzres.dll’ has no imports
10a0.3b48: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume1\Windows\System32\tzres.dll)
10a0.3b48: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\tzres.dll
10a0.3b48: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000f14 (hFile=0000000000000f0c) with 0xc0000022 -> STATUS_TRUST_FAILURE
10a0.3b48: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume1\Windows\System32\tzres.dll [avoiding WinVerifyTrust]
10a0.3b48: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000f0c (hFile=0000000000000f14) with 0xc0000022 -> STATUS_TRUST_FAILUREindent preformatted text by 4 spaces

To begin, launch the VirtualBox Manager then select the virtual machine from the list pane you would like to export. Make sure the operating system you are exporting is supported by Hyper-V. Click the File menu then click Export Appliance…

Select the virtual machine again, then click Next.

Choose the location where you would like to store the virtual machine file, select the OFV 2.0 format then click Next .

Click Export then wait while the appliance is exported; this can take some time depending on the size of the virtual machine.

Before you can begin the conversion, we will need to use a uncompressing utility such as 7-zip to extract the contents of the OVF file we just exported.

Our next step is to import the VM into Microsoft’s Hyper-V software. Hyper-V does not natively support the Open Virtual Format. Initially, I attempted to convert the VM using Microsoft’s free utility called Virtual Machine Converter and the built-in PowerShell cmdlet. I experienced nothing but frustration getting it to work; see the proof below.

After some web searching, I came across a free utility from StarWindcalled V2V Image Converter designed just for converting different types of virtual hard disk formats. First, you need to sign up for the free download, which will be sent to you in an email link. After receiving your free download, proceed to download and setup StarWind Converter.

Launch the StarWind V2V Image Converter software then click Next.

Choose Local file as your source then click Next .

Choose the format you would like to convert the image to. Hyper-V supports VHD and VHDX formats. VHDX is an improvement over the older virtual hard disk format, supporting up to 64 TBs of storage. Because this is a Windows XP VM, I will stick with a fixed VHD option called VHD Pre-allocated image.

Browse to where on your hard disk you would like to store the converted image.

Select the destination of the VHD file. In my case, this will be used locally, so, I will stick with the default.

Wait while the vmdk file is converted. The larger the vhd, the longer it will take.

Import Virtual Machine into Hyper-V

The next step is to see if it works. Launch Hyper-V in Windows 10, click New > Virtual Machine then click Next . Go through the wizard and configure your virtual machine with the appropriate settings. When you arrive at the Connect Virtual Hard Disk section, choose Use an existing virtual hard disk , click Browse… , then open the vhd file we converted earlier then click Next.

Click Finish to confirm your configuration.

Proceed to launch your virtual machine and there you have it. Your Oracle VirtualBox VM is now up and running in Hyper-V.

That wasn’t so bad. Looking for more tutorials on VMs? Check out our post on connecting your virtual machine to the Internet.

Admin
o356cloudexperts