But since it's a "Linux" VM, it doesn't know how to read the filesystem of the Big Sur installer. Which just happens to be a USB drive with the Big Sur installer on it. Well this is promising! Parallels sees the disk I want to boot from. Just as a test, what if I take that same USB drive and boot a "Linux" VM with it? Maybe in this case just boot from the USB device, without trying to interpret what is on the device? Uhh, what? In what seems to be a recurring theme, Parallels is making decisions on my behalf, assuming it knows what I really want. So let's just try the same steps, but with our Big Sur installer USB drive: Well this is promising! We can select the UEFI boot info from our "hard disk" (that is backed by the USB disk we selected), and we boot right into our linux distro installer (or whatever we picked to test). Here you can select the USB device that has the OS you wish to boot:Īs a warm-up, let's just try to boot with a bootable ARM Linux installer: But there is a workaround!Īdd a hard disk, and when you specify the backing for the hard disk, select "Physical disk". You can connect a USB device, but UEFI will never see it. I think the problem exists on multiple levels.ġ) This Parallels beta doesn't seem to be able to boot directly from USB devices.
0 Comments
Leave a Reply. |