Bug 804579 – Gentoo Guest on VirtualBox 6.1.22 Windows 10 Pro host, CDROM is NOT working on kernel ver 5.10.52, but was working on kernel ver 5.10.27

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description sevilla.larry 2021-07-27 03:27:58 UTC]

Host: Windows 10 Pro x64
VirtualBox 6.1.22

Guest: Gentoo

when using the kernel ver 5.10.52, CDROM is NOT working
while using the previous ver 5.10.27, CDROM is working


Reproducible: Always

Steps to Reproduce:
1. emerge --sync
2. updated the gentoo-sources from 5.10.27 to 5.10.52
3. re-compile the kernel ver 5.10.52
4. reboot, CDROM did NOT work well

If I use the kernel 5.10.27, CDROM is working


Expected Results:  
CDROM should still be working when upgrading kernel version

5.10.52
initially /dev/cdrom is linked/pointed to /dev/sr0
after attaching an ISO to CDROM, /dev/cdrom is removed

the bug is existing in x32(x86) and x64,
regardless if the CDROM is an IDE or SATA

[Comment 1 Mike Pagano 2021-08-01 16:24:47 UTC]

can you attach dmesg of working and non-working kernel ?

Can you paste emerge --info into a comment ?

[Comment 2 sevilla.larry 2021-08-02 01:16:03 UTC]

CD-ROM Working kernel: 5.10.27

dmesg
  x32 https://pastebin.com/YAJ82J0L
  x64 https://pastebin.com/0fN1zZXr

emerge --info
  x32 https://pastebin.com/sGeWq7wF
  x64 https://pastebin.com/W3bSDVvS



CD-ROM NOT working kernel: 5.10.52

dmesg
  x32 https://pastebin.com/1pZr7t50
  x64 https://pastebin.com/7dU6ua4B

emerge --info
  x32 https://pastebin.com/Ju8rZXEw
  x64 https://pastebin.com/0BnfVjMH

[Comment 3 sevilla.larry 2021-08-10 23:34:17 UTC]

Upgrading VirtualBox from 6.1.22 to 6.1.26 seems SOLVED the problem.

Conclusion:

VirtualBox 6.1.22 + Linux Kernel 5.10.27 Compatible
VirtualBox 6.1.26 + Linux Kernel 5.10.52 Compatible

VirtualBox 6.1.22 + Linux Kernel 5.10.52 NOT compatible

[Comment 4 Mike Pagano 2021-08-24 11:21:38 UTC]

As newer versions of VirutalBox seemed to have solved this, I am closing for now. Let us know if this breaks again