Hi,
I'd would like to boot my native Linux installation from within Sculpt using Virtualbox. First, let me briefly describe what I have done so far:
I created a raw disk image that contains the relevant partitions (ESP, root and home), added the Block devices to the vfs of Virtualbox, and routed the Block sessions to the corresponding part_blk server. I also made the EFI firmware file available to Virtualbox. I created a vbox file and tested it on another Linux system. However, when using this vbox file on sculpt, I noticed that vbox does not respect the '<Firmware type="EFI"/>', i.e. neither my boot manager nor the UEFI shell appears. I had a look in the Genode repository and noticed that there is a vbox patch that removes (ifdef 0) the Nvram initialisation which is supposed to happen if the firmware type is EFI.
Thus it appears that EFI support has been 'patched-out' from the virtualbox port. Is this intentional? Are there any major blockers that prevent us from using Virtualbox with some EFI firmware?
Cheers Johannes
Hello,
On 06.02.19 14:00, Johannes Schlatow wrote:
Hi,
I'd would like to boot my native Linux installation from within Sculpt using Virtualbox. First, let me briefly describe what I have done so far:
I created a raw disk image that contains the relevant partitions (ESP, root and home), added the Block devices to the vfs of Virtualbox, and routed the Block sessions to the corresponding part_blk server. I also made the EFI firmware file available to Virtualbox. I created a vbox file and tested it on another Linux system. However, when using this vbox file on sculpt, I noticed that vbox does not respect the '<Firmware type="EFI"/>', i.e. neither my boot manager nor the UEFI shell appears. I had a look in the Genode repository and noticed that there is a vbox patch that removes (ifdef 0) the Nvram initialisation which is supposed to happen if the firmware type is EFI.
Thus it appears that EFI support has been 'patched-out' from the virtualbox port. Is this intentional? Are there any major blockers that prevent us from using Virtualbox with some EFI firmware?
It is not clear, why this happened. Since nobody asked for this feature, it just went unnoticed. Fell free to enable it and see where you get. At least no blockers are known.
Cheers,
Alex.
Hi Johannes,
I'm interested in this setup too. Did you manage to get it to work?
Cheers Sid
On 2/6/19 2:00 PM, Johannes Schlatow wrote:
Hi,
I'd would like to boot my native Linux installation from within Sculpt using Virtualbox. First, let me briefly describe what I have done so far:
I created a raw disk image that contains the relevant partitions (ESP, root and home), added the Block devices to the vfs of Virtualbox, and routed the Block sessions to the corresponding part_blk server. I also made the EFI firmware file available to Virtualbox. I created a vbox file and tested it on another Linux system. However, when using this vbox file on sculpt, I noticed that vbox does not respect the '<Firmware type="EFI"/>', i.e. neither my boot manager nor the UEFI shell appears. I had a look in the Genode repository and noticed that there is a vbox patch that removes (ifdef 0) the Nvram initialisation which is supposed to happen if the firmware type is EFI.
Thus it appears that EFI support has been 'patched-out' from the virtualbox port. Is this intentional? Are there any major blockers that prevent us from using Virtualbox with some EFI firmware?
Cheers Johannes
Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users
Hi Sid,
unfortunately, I was not able to get it working. I'm stuck at an assertion error and haven't found the time yet to have a deeper look at what is going wrong.
What I did so far: - I re-enabled the mNvram initialisation in ConsoleImpl.cpp by removing the '#if 0'. - I added the -DVBOX_WITH_EFI to VBOX_CC_OPT.
What I get is an assertion error:
[runtime -> archlinux -> vbox] Using VMX virtualization extension.[0m [runtime -> archlinux -> vbox] EMT-0 EMT-0 !!Assertion Failed!! EMT-0 Expression: page_idx <= GMM_PAGEID_IDX_MASK EMT-0 Location : src/virtualbox5/spec/nova/sup.cc(423) int SUPR3CallVMMR0Ex(PVMR0, VMCPUID unsigned int, uint64_t, PSUPVMMR0REQHDR)
On Thu, 7 Feb 2019 18:58:01 +0100 Sid Hussmann sid.hussmann@gapfruit.com wrote:
Hi Johannes,
I'm interested in this setup too. Did you manage to get it to work?
Cheers Sid
On 2/6/19 2:00 PM, Johannes Schlatow wrote:
Hi,
I'd would like to boot my native Linux installation from within Sculpt using Virtualbox. First, let me briefly describe what I have done so far:
I created a raw disk image that contains the relevant partitions (ESP, root and home), added the Block devices to the vfs of Virtualbox, and routed the Block sessions to the corresponding part_blk server. I also made the EFI firmware file available to Virtualbox. I created a vbox file and tested it on another Linux system. However, when using this vbox file on sculpt, I noticed that vbox does not respect the '<Firmware type="EFI"/>', i.e. neither my boot manager nor the UEFI shell appears. I had a look in the Genode repository and noticed that there is a vbox patch that removes (ifdef 0) the Nvram initialisation which is supposed to happen if the firmware type is EFI.
Thus it appears that EFI support has been 'patched-out' from the virtualbox port. Is this intentional? Are there any major blockers that prevent us from using Virtualbox with some EFI firmware?
Cheers Johannes
Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users
Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users
-
Alexander Boettcher -
Johannes Schlatow -
Sid Hussmann