VirtualBox

Ticket #6837 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

EFI bios failt to detect HDD's attached to the SATA -> fixed in SVN

Reported by: LeXa2 Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 3.2.0 Keywords: EFI AHCI SATA
Cc: Guest type: other
Host type: other

Description

When the virtual machine is set to use EFI it is impossible to boot from any disk attached to the emulated SATA controller.

To reproduce: Create a new VM, set it to use EFI, delete all disk controllers. Then add one SATA AHCI controller and attach any HDD to it (say, to the SATA port 0). Try to power on the machine and it will get into EFI shell after some time. Use "map" command to display current device mappings and notice that there are no maps defined. Use "devices" command and notice that there are no block disk devices found.

Power off the vm, delete SATA controller, add standard IDE instead and attach an HDD to it. Try to boot up the VM, get into EFI shell, issue "map" and notice that there are block devices maps found. Issue "devices" and notice that the IDE controller and HDD were detected.

Confirmed to happen on Virtual Box 3.2.0 on CentOS 5 32bit PAE (RHEL5) host and on Fedora 9 32bit PAE host.

Change History

comment:1 Changed 4 years ago by LeXa2

Still happens in VirtualBOX 3.2.6. Are there any plans to fix this bug? I consider it to be a major one as virtual SATA controller gives somehow better performance comparing with virtual PATA, and at the moment is it simply impossible to boot into OS installed on the disk connected to the SATA controller when EFI is on.

comment:2 Changed 4 years ago by frank

  • Priority changed from major to minor

Minor importance. There is actually no reason to use EFI for a Linux guest.

comment:3 Changed 4 years ago by LeXa2

Where did you spot I've been talking about linux guest? Linux was mentioned only as a host OS I had tested bug to be present on. I'm pretty sure that this bug also applies to the Windows and Mac OS X hosts. For example this means that it is currently impossible to boot Mac OS X Server guest on the Mac OS X host when VM is set to use SATA instead of PATA. As SATA controller emulation in VBox is known to be more efficient than PATA I consider this bug to be pretty major one.

comment:4 Changed 4 years ago by frank

  • Priority changed from minor to major

Seems I mixed this up. But even for Mac OS X server guests there are other more important things to fix.

comment:5 Changed 4 years ago by Hachiman

  • Summary changed from EFI bios failt to detect HDD's attached to the SATA to EFI bios failt to detect HDD's attached to the SATA -> fixed in SVN

Please re-check when new major release will be available.

comment:6 Changed 3 years ago by LeXa2

Is it expected to work in VBox 3.2.10?

comment:7 Changed 3 years ago by frank

No, the next major release will be 4.0.0.

comment:8 Changed 3 years ago by ni81036

Although you'll be able just drop newer firmware in 3.2 binary dir and get this feature too.

comment:9 Changed 3 years ago by ni81036

  • Status changed from new to closed
  • Resolution set to fixed

comment:10 Changed 3 years ago by frank

  • Status changed from closed to reopened
  • Resolution fixed deleted

This ticket will be closed when the new release is out.

comment:11 Changed 3 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use