#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!)
Attachments (6)
Change History (13)
by , 9 years ago
by , 9 years ago
Attachment: | Screenshot_2016-08-04_11-47-33.png added |
---|
by , 9 years ago
Attachment: | Screenshot_2016-08-04_11-47-50.png added |
---|
by , 9 years ago
Attachment: | Screenshot_2016-08-04_11-48-09.png added |
---|
by , 9 years ago
by , 9 years ago
comment:1 by , 9 years ago
comment:2 by , 9 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 , 9 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 , 9 years ago
I could reproduce on 5.0.26. I think the magic combo is the IDE controller AND USB 3.0.
Steps:
- Create New VM
- Name: TestF24
- Type: Linux
- Version: Fedora (64-bit)
- Create new disk, 8GB, dynamic
- Settings
- Attach Live CD to IDE controller : Fedora LXDE Live CD x86_64-24-1.2.iso
- USB -> enable 3.0
- Install to disk
- Shutdown
- Remove Live CD
- Start
- dnf update (this should get kernel 4.6.5-300 as of today)
- Reboot
- Error after 23s
comment:6 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
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 , 9 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.
Same or similar problem on kernel 4.6.5-300