VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1552 - 1554 of 16363)

Ticket Resolution Summary Owner Reporter
#1587 fixed Install guest addons on LFS guest Thomas
Description

Installing the guest addons in a guest machine fails when "distro" is Linux From Scratch. There are checks for "/usr/X11R6/lib/modules" while in LFS there is "/usr/X11R7.2/lib/X11/modules" and some other mismatches.

To see whether it is LFS, you may want to look for "/etc/lfs-release". Than you will know that the

  • boot-scripts are in "/etc/rc.d/init.d/"
  • X configuration should be "/etc/X11/xorg.conf"
  • X11 modules dir can be assumed as "/usr/X11R6/lib/X11/modules" (since there is a compatibility symlink from /usr/X11R7.x to /usr/X11R6)

Do you any chance to add this to the VBoxLinuxAdditions.run script?

Btw, I tested this on VB-1.5.6, I'll test it again on 1.6.x when x becomes greater than zero ;-)

#1588 duplicate VMs drop out of full screen when switching video modes James
Description

I just upgraded to v1.6.0 and I have noticed a usability issue involving the full screen feature. I run VirtualBox on Ubuntu, and I like to have a separate desktop devoted to my virtual machine when I need to use Windows or another OS. I usually start the VM, switch desktops, and continue doing whatever I was doing while the guest OS loads.

In 1.5.6, this usage pattern worked great for me. With 1.6.0, the VM drops out of full screen every time the guest wants to change the screen size or video mode, which happens several times throughout the loading sequence of the OS. This is annoying because:
(1) The VM window pops back onto my current desktop, where I am working, instead of staying out of my way where I want it to be; and
(2) I have to tell the VM to use full screen again.

Another side effect of this new behavior is that my VMs will not "remember" that I want them to be full screen after I shut them down and start them back up again. A fix would be greatly appreciated. Sorry if this issue has already been addressed.

#1589 fixed Keyboard inoperative on Solaris 10 or Solaris 8 guest Tim Small
Description

Host: 64bit Debian 4.0 (Etch)

Tested on 1.5.6 (S8 and S10 guest), and 1.6.0 (S10 guest), keyboard input works correctly on both versions of the Solaris installer up until the point where the kernel is booted (i.e. kbd input to boot loader works fine). S10 appears to recognise no keyboard input, S8 on 1.5.6 doesn't accept anything until the return key is pressed, and then it behaves as if the 'a' key is being held down.

S10 guest keyboard input appears to work OK on 1.6.0 when ACPI is disabled.

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