Please drop a comment if you know something about this. Whether there is a drawback in terms of performance or whatsoever I don’t know. So instead of the steps above you can simply call the script with -format=vmware and use the resulting image. With this invokeVBoxManage convertfromraw /path/to/input_image.bin /path/to/vbox_image.vdi The simple wayAs I found out later, Virtualbox also supports the VMDK format from VMware. The same post also tells that the failed conversion could simply be done outside the chroot, so I chose that solution.The image to pass as input parameter to VBoxManage can be found under src/build/images/x86-generic/latest/vm_temp_image.bin relative to the checkout directory.
I didn’t encounter any so far, but switching to bridged networking is said to help in this case. I also heard and read of troubles with NAT networking. The machine didn’t recognize it.What helped was to change the adapter type for the virtual network interface to Intel PRO/1000 MT Desktop in the network settings for the VM. In my case the network connection for the virtual machine didn’t work right away.
0 kommentar(er)
