VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1564 - 1566 of 16363)

Ticket Resolution Summary Owner Reporter
#16562 obsolete mouse locks up in (some) VMs after some uptime when using vbox after 5.1.10 Harry M
Description

Using 5.1.12 or later on a CentOS 6.8 host, certain VMs experience a loss of response to mouse clicks (both left and right) after some amount of uptime (usually a day or so). This was also observed on 5.0.30 and after. MI is enabled, and ALL VMs are configured to use tablet device.

The guest most likely to have the problem is an ArchLinux variant called obarun (obarun.org for more info).

GAs are up-to-date on all guests. Guests are generally kept up to date on system software as well.

Workaround has been to downgrade to 5.1.10 (or 5.0.28) where the problem is not experienced.

#17095 obsolete Logfiles reporting "vminfo Error: Guest Property: Failed to query '/VirtualBox/HostInfo/VRDP/ActiveClient': VERR_NOT_SUPPORTED" after resume from hibernate in guest VM Harry M
Description

Don't laugh. After resuming from hibernation in a Devuan 1.0 guest (with 5.1.26 GAs built from virtual CD), log messages begin appearing by the truckload:

vminfo Error: Guest Property: Failed to query '/VirtualBox/HostInfo/VRDP/ActiveClient': VERR_NOT_SUPPORTED

Granted, hibernating within a VM is not one of the smartest things a user can do, but there may be some reason someone feels driven to try this. Using VirtualBox's own save state/restore state feature is a much better approach, not to mention about 80-1000 times faster.

Host is CentOS 6.9, with VBox 5.1.26.

The workaround is to not to do this. Use the save/restore state feature of VBox instead. Duh.

#19033 fixed Guest Additions Build test for Systemd is not robust => Fixed in SVN Harry M
Description

The test for the presence or not of systemd in the GA build process is not robust enough for all cases. Currently, the use_systemd() in routines.sh relies on criteria which may not be true for all cases where systemd is not in use. One such example is Artix, an archlinux variant without systemd, but there are likely to be others.

On Artix, as the example here, the routine tests if /sbin/init is a symlink, which it is. But the routine (incorrectly) assumes that such a link is indicative of a systemd environment.

The problem is that when the installer tests for systemd when it is not present but it thinks it really is present, apparently, the steps the GA build are not followed to completion.

I am not certain what a truly robust test would be, but maybe looking at files that are only created in the presence of systemd would be better (maybe something under /etc?). Keep in mind that "shim" packages on non-systemd platforms often install similarly-named files and programs to those in systemd, so relying on those may also not be completely robust.

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