VirtualBox

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#15747 closed defect (fixed)

VirtualBox 5.0.26 won't boot Linux 4.6.4 on Fedora 24

Reported by: R D Owned by:
Component: VMM Version: VirtualBox 5.0.26
Keywords: Cc:
Guest type: Linux Host type: Linux

Description

  • Host: Fedora 24 Linux 4.6.4-301.fc24.x86_64
  • VirtualBox: 5.0.26 (also happens on 5.0.24)
  • Guest: Fedora 24 LXDE spin. Linux 4.6.4-301.fc24.x86_64

(Linux 4.6.3-300.fc24.x86_64 works!)

Change History (13)

by R D, 8 years ago

Attachment: VBox.log added

comment:1 by R D, 8 years ago

Same or similar problem on kernel 4.6.5-300

comment:2 by R D, 8 years ago

Figured out that the problem is the default IDE controller (+ CDROM) that is added for a new instance. If I remove the IDE controller and add a new CDROM to the SATA controller, everything works.

comment:3 by Frank Mehnert, 8 years ago

Cannot reproduce this with 5.0.27 nor 5.1.3. I'm not aware of any corresponding changes but could you test a test build from here? I used Fedora 24 with Linux 4.6.5-300.

comment:4 by R D, 8 years ago

I could reproduce on 5.0.26. I think the magic combo is the IDE controller AND USB 3.0.

Steps:

  1. Create New VM
    • Name: TestF24
    • Type: Linux
    • Version: Fedora (64-bit)
    • Create new disk, 8GB, dynamic
  2. Settings
    • Attach Live CD to IDE controller : Fedora LXDE Live CD x86_64-24-1.2.iso
    • USB -> enable 3.0
  3. Install to disk
  4. Shutdown
  5. Remove Live CD
  6. Start
  7. dnf update (this should get kernel 4.6.5-300 as of today)
  8. Reboot
  9. Error after 23s

comment:5 by Frank Mehnert, 8 years ago

Good catch! I see the same problem if I enable USB3.

comment:6 by Frank Mehnert, 8 years ago

Resolution: fixed
Status: newclosed

In our opinion this is a bug in the Linux kernel which was recently introduced. This bug will probably never be triggered on real hardware.

comment:7 by Frank Mehnert, 8 years ago

For reference, see here. VBox 5.1.4 contains a workaround but once this patch is added to the kernel, our workaround is no longer necessary.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use