#Mac os ext4 driver code
Everything that happens from then on is due to the code inside the boot sector. Assuming you're using a legacy boot for the VM (not EFI), then all the BIOS does is read the first sector into a memory location and then jump to it. VirtualBox has absolutely no idea about the contents of the disk.
Attachments VBox.log Log (failing to boot) (87.8 KiB) Downloaded 94 times vm_info.txt VM info (4.01 KiB) Downloaded 92 times Biggles Posts: 3 Joined: 1. Virtual machine information and log file (for failing to boot scenario) are attached.
#Mac os ext4 driver driver
This makes me believe that it is something to do with either the Paragon ExtFS driver or the way that the external drive is mounted. It still runs flawlessly on that computer.Ĭopying the virtual disc image to the hard drive of my Mac means that the virtual machine boots and runs flawlessly. The virtual machine and the virtual disc image were both originally created on a Linux computer (running Gentoo Linux, kernel version 3.16.5 and VirtualBox 4.3.18). I also found in the VBox.log file this line about the partition on which the virtual disc image is stored:Ĭode: Select all Expand view Collapse view 00:00:00.723826 File system of '/Volumes/webapps/vm/webapps.vdi' is unknown I'm not sure if this is causing a permissions problem for VirtualBox.Ĭode: Select all Expand view Collapse view /dev/disk2s1 on /Volumes/webapps (ufsd_ExtFS, local, noowners) I have noticed that the file system is mounted as follows. I have tried making the virtual disc read/writeable by everyone, but the problem still occurs.
The virtual disc image I am booting from uses a separate boot partition because it stores everything else in an encrypted LVM container. Since it can't even show the boot menu, then I assume it can't find the GRUB configuration files, which are usually stored in the partition containing /boot. Error displayed when failing to boot failure_to_boot_extfs.png (5.27 KiB) Viewed 2209 timesĪ list of GRUB errors tells me (without much detail) that this can be caused by GRUB failing to find something it needs to continue with the boot process.
0 kommentar(er)
