I added a ticket on their support site. I may go digging around in their source code if I get some time. This will probably have to be done in the guest BIOS, though.
https://www.virtualbox.org/ticket/16809
Read from usb storage device
Re: Read from usb storage device
Project: OZone
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Re: Read from usb storage device
Good news!
The VirtualBox bug guy has decided that this isn't a bug...
He "suggests" that you just don't use PCI Express in VirtualBox.
At least he could have lied and said that they will look into it.
The VirtualBox bug guy has decided that this isn't a bug...
He "suggests" that you just don't use PCI Express in VirtualBox.
At least he could have lied and said that they will look into it.
Project: OZone
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Re: Read from usb storage device
Hi,
The PCI Firmware Specification does say "If the operating system does not natively comprehend reserving the MMCFG region, the MMCFG region must be reserved by firmware."; but (excluding "OS and hardware as single product" scenarios that don't apply to VirtualBox) firmware has no way to know if the OS that the end user might decide to install does or doesn't natively comprehend reserving the MMCFG region, and therefore firmware needs to make "safe assumptions" (and assume that the MMCFG region must be reserved by firmware).
For my case, it doesn't really matter too much - it just means that anyone using VirtualBox wins a free warning in the OS's event log.
Cheers,
Brendan
That guy is a fool.SpyderTL wrote:Good news!
The VirtualBox bug guy has decided that this isn't a bug...
The PCI Firmware Specification does say "If the operating system does not natively comprehend reserving the MMCFG region, the MMCFG region must be reserved by firmware."; but (excluding "OS and hardware as single product" scenarios that don't apply to VirtualBox) firmware has no way to know if the OS that the end user might decide to install does or doesn't natively comprehend reserving the MMCFG region, and therefore firmware needs to make "safe assumptions" (and assume that the MMCFG region must be reserved by firmware).
Exactly - it breaks backward compatibility for the sake of avoiding spending 5 minutes on a trivial change.SpyderTL wrote:He "suggests" that you just don't use PCI Express in VirtualBox.
For my case, it doesn't really matter too much - it just means that anyone using VirtualBox wins a free warning in the OS's event log.
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
Re: Read from usb storage device
Given that E820 is PC specific and PCI is not PC specific, the PCI spec obviously can't say that E820 _MUST_ do anything, since E820 might not even exist. Even newer PC's might not have E820 if hey only support UEFI and don't support legacy BIOS.SpyderTL wrote:Good news!
The VirtualBox bug guy has decided that this isn't a bug...
He "suggests" that you just don't use PCI Express in VirtualBox.
At least he could have lied and said that they will look into it.
Further, the PCI spec doesn't really have a say when it comes to other "standards", except for giving recommendations. If the memory map doesn't include everything then it's invalid. The firmware must include reserved areas in the memory map(s) as well.