There, in Guided (not Expert) mode, I identified the ISO, specified a target VM name and location, selected Enable EFI (special OSes only), and chose Create a Virtual Hard Disk Now, allowing enough space for the full size of the ISO. For that, I went into VirtualBox > menu > Machine > New. iso, and seeing if VirtualBox would use the ISO. I started with what appeared easiest – namely, changing the. Now I tried to repeat those approaches in VirtualBox. Another complex solution involved the Plop tool. A more complex solution would boot an existing VM with an interloper – that is, a secondary operating system – and then use that interloper to run tools or commands that would clone the bootable USB drive, or the image file containing the contents of that drive, to an existing but non-running VM. iso, and then use that ISO to create a VM. iso, or if necessary use a free converter to convert. Alternately, it seemed I should be able to change the image file’s extension from. Among those methods, there was supposedly an option to convert the. The methods discussed in the other post did, in fact, try to use those images to create a VMware VM. So I already had those images, if I wanted to try to use them in VirtualBox. While those images were not identical, Balena Etcher and Rufus were able to make working bootable Ubuntu USB drives from them. The other post describes how I used Ubuntu’s Disks tool and dd command to create images of the bootable USB drive. Therefore, I decided to start this separate writeup, reviewing some of those approaches in the context of VirtualBox rather than VMware Player. Despite multiple attempts using different approaches, that effort was striking out. Another post describes my efforts to convert a customized bootable Ubuntu USB installation to a virtual machine using VMware Workstation Player.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |