VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (178 - 180 of 16363)

Ticket Resolution Summary Owner Reporter
#2847 fixed <Henkan_Mode> Key on Japanese keyboard is not recognized on Solaris host => fixed in SVN yukie
Description

<Henkan_Mode> key on Japanese keyboard is not worked correctly on Solaris.
Because the meaning of key code is different.

  • <Henkan_Mode> Key is recognized as <kanji(0xff21)> on Solaris host.
  • <Henkan_Mode> key is recognized as <Henkan_Mode(0xff23)> on Ubuntu host.

This was fixed in VirtualBox 2.06 by ticket 2263.
But it is not fixed in VirtualBox 2.10.
I opened a new ticket as a follow to #2263.

#4874 duplicate NT 4 CX8 bug workaround and VirtualBox Yuhong Bao
Description

There has been several bug reports like bug #774 relating to VIA CPUs not been able to run XP where the NT 4 CX8 workaround appears to have been enabled on the host. (the host /proc/cpuinfo has no cx8 listed in flags)

Background: NT 4 pre-SP4 had a bug where it would not boot if CPU vendor ID returned by CPUID EAX=0 was not "GenuineIntel", "AuthenticAMD", or "CyrixInstead" and the CX8 feature bit was set. As a result of this bug, all other CPU vendors had to provide a way to clear the CX8 feature bit, usually via a MSR, which was usually exposed as a BIOS option.

Unfortunately this workaround came to bit MS later when it decided to require CX8 for XP, otherwise XP won't boot and the loader will throw up an error message.

What MS had to do was to add code to XP to detect non-Intel/AMD/Cyrix CPUs with CX8 feature bit cleared and add CPU vendor specific code to again set the CX8 feature bit.

Geoff Chappell disassembled the Windows CPUID code and wrote this about this issue: http://www.geoffchappell.com/viewer.htm?doc=studies/windows/km/cpu/cx8.htm

What was probably happening is that the zero CX8 bit of the host CPU was being passed through by VirtualBox to the VM, but XP's manipulation of MSRs in response to the zero CX8 bit to set it back to one failed because XP was running in a VM, where MSRs were being virtualized. Thus, XP had to throw up an error message and fail the boot.

For users who are encountering this problem: Look in the host system's BIOS for a BIOS option that has something like the word "CX8" or "NT4" in it. Try changing that option.

#16626 obsolete Licence for EFI / FatPkg should be changed Yuhong Bao
Description

http://www.virtualbox.org/svn/vbox/trunk/src/VBox/Devices/EFI/Firmware/FatBinPkg/License.txt still has the term of "Additional terms: In addition to the forgoing, redistribution and use of the code is conditioned upon the FAT 32 File System Driver and all derivative works thereof being used for and designed only to read and/or write to a file system that is directly managed by Intel's Extensible Firmware Initiative (EFI) Specification v. 1.0 and later and/or the Unified Extensible Firmware Interface (UEFI) Forum's UEFI Specifications v.2.0 and later (together the "UEFI Specifications"); only as necessary to emulate an implementation of the UEFI Specifications; and to create firmware, applications, utilities and/or drivers." This was removed by upstream last year.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy