Ticket #15221 (new defect)
VirtualBox 5.0.16 Guest Additions fail to install under RHEL 5.11 64-bit
Reported by: | Urhixidur | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 5.0.16 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | other |
Description
The build fails, and the RHEL 5.11 system becomes unusable: it keeps getting a kernel panic ("not syncing") at boot time.
Attachments
Change History
Changed 6 years ago by Urhixidur
-
attachment
VBox 5.0.16 Guest Additions failure
added
comment:1 Changed 6 years ago by frank
Please attach the corresponding VBox.log file of that VM session.
comment:2 Changed 6 years ago by frank
You run your EL 5.11 guest with 512MB RAM. Please increase the amount of guest RAM to 640MB. Do you still have this issue after doing that? If so, any chance to get a guest log which contains such a kernel panic? Configuring a serial port which outputs to a host file might help.
comment:3 Changed 6 years ago by Urhixidur
What do you mean, 512 MiB? I had the VM configured to run with 1536 MiB! I'll try to figure this out.
comment:4 Changed 6 years ago by frank
Sorry, my fault. 1536 MiB should be really sufficient. But still, a guest log containing the kernel panic would be helpful.
comment:5 Changed 6 years ago by Urhixidur
I paused the VM as it panicked and got a snapshot of that.
Changed 6 years ago by Urhixidur
-
attachment
Screenshot from 2016-03-14 101703.png
added
Screenshot of kernel panic
Changed 6 years ago by Urhixidur
-
attachment
VBox from 2016-03-14 101703.log
added
VBox.log of kernel panic
comment:6 follow-up: ↓ 7 Changed 6 years ago by frank
Unfortunately the actual kernel panic is not visible (only the callstack is). According to the hex code it's indeed a normal kernel panic. When do it happen? Does it also happen if you don't have the vboxsf module loaded (and no shared folders shared)?
comment:7 in reply to: ↑ 6 Changed 6 years ago by Urhixidur
Replying to frank:
Unfortunately the actual kernel panic is not visible (only the callstack is). According to the hex code it's indeed a normal kernel panic. When does it happen? Does it also happen if you don't have the vboxsf module loaded (and no shared folders shared)?
It never makes it that far. While the system is rebooted, as it starts up it goes into a kernel panic and loops back to booting again. Sometimes it even panics as it is going down. (Normally I must then restore the VM to its pre-Guest-Additions state) You can experience this yourself by grabbing a RHEL 5.11 64-bit installation DVD and building a fresh system, then inserting the Guest Additions and running VBoxLinuxAdditions.run. Since RHEL is not freely accessible, I should try this with CentOS 5.11 and see if the same thing happens.
Note that RHEL 5.11 32-bit has no problem with the Guest Additions.
Log of the failed install