VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1462 - 1464 of 16363)

Ticket Resolution Summary Owner Reporter
#12370 obsolete File Mangled When Accessed in VB thosoc
Description

I would like to report some strange thing where content of files appeared to be mangled and truncated in several places when they are accessed on a virtual OS. In my case, the virtual OS is CentOS running in a VirtualBox 4.2.18, which resides in a MAC MINI running Lion. I've noticed this behavior a few times but had not the time to track it down until now.

I am including a couple of screenshots for illustration. The file "Native-screenshot.png" shows a .cpp source file as it was accessed locally using vi in the native MACOS where the code block on lines 4742-4750 shows the #else-if block and is followed by the function ACE_OS::thr_key_used. On the other hand, the file CentOS-screenshot.png shows the same code block that is mangled and truncated starting from line 4742 where the chunk of codes starting from ACE_OS::thr_key_used() to vx_execae() was chopped off.

Thank you for the help.

Thosoc

#18530 invalid xorg couldn't open module vboxvideo thorstenhirsch
Description

There seems to be a problem with the linux vboxvideo module in the latest guest additions. This is what's in the xorg log file:

[   229.545] (==) Matched vboxvideo as autoconfigured driver 0
[   229.545] (==) Matched vboxvideo as autoconfigured driver 1
[   229.545] (II) LoadModule: "vboxvideo"
[   229.546] (WW) Warning, couldn't open module vboxvideo
[   229.546] (II) UnloadModule: "vboxvideo"
[   229.546] (II) Unloading vboxvideo
[   229.546] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
[   229.547] (==) Matched vboxvideo as autoconfigured driver 0
[   229.547] (==) Matched vboxvideo as autoconfigured driver 1
[   229.547] (II) LoadModule: "vboxvideo"
[   229.547] (WW) Warning, couldn't open module vboxvideo
[   229.547] (II) UnloadModule: "vboxvideo"
[   229.547] (II) Unloading vboxvideo
[   229.547] (EE) Failed to load module "vboxvideo" (module does not exist, 0)

But the module was successfully loaded, here's what lsmod says:

vboxvideo              36864  2
ttm                   106496  1 vboxvideo
drm_kms_helper        172032  1 vboxvideo
drm                   401408  5 drm_kms_helper,vboxvideo,ttm

And this is the output of dmesg:

[    4.811273] vboxvideo 0000:00:02.0: fb0: vboxdrmfb frame buffer device
[    4.824322] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0

It's Ubuntu 18.04.2 with kernel 4.15.0-46. All packages are up-to-date. I already updated VBoxGuestAdditions from 6.0.4 to 6.0.5-129665, but the problem remains the same.

#5027 obsolete VirtualBOX 3.X.X Host-Only-Network-Connection crashes Live Messenger 2009 video Thorsten
Description

Hello!

My Host OS is Windows Vista 64 Ultimate SP2.

VirtualBOX installs a VirtualBOX-Host-Only-Network-Conection. This network conection crashes the Windows Live Messenger video conection. The Windows Live Messenger show this message: "Messenger is not availible. Please try again later. (0x8ac70013)"

If the VirtualBOX-Host-Only-Network-Conection is disable the Windows Live Messenger video conection works smoothly.

Best regards, Thorsten :-)

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