VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1369 - 1371 of 16363)

Ticket Resolution Summary Owner Reporter
#2408 fixed Problems with USB on Windows Host (XP and Vista) xfernandez
Description

I started with only 1 Gigabyte of RAM on the host system (Windows Vista). With this amount of RAM:

· VirtualBox can start the VM · It seems impossible to control USB devices (in general, not just the IO card) · The system becomes very slow and is likely to hang after awhile

I added 1 Gigabyte of RAM to the system and noticed improvements: · The system does not become slow nor hang. · I was able to access a pen drive and a standard Bluetooth dongle from the VM with no problems. · I was able to access the IO card with problems (described below).

It's necessary to have 2 Giga of Ram in the Host?

In the probes I use an IOCard that it's connected via USB. This IOCard has 3 bluetooth devices. This 3 devices are detected on USB filter creation. And I only connect the IOCard when the VM is running. In general the VM detects the bluetooth USB devices (My guest is a Linux and I use the hciconfig command).

But In some cases, it appears problems: · Sometimes appears the error: "USB device is busy with a previous request, please try again" Result Code: E_INVALIDARG (0x80070057) · Simetimes VM detects 3 devices, other times 2 devices, 1 device, 0... I can't understand the behavior.

If you need more information, no doubt of ask me.

#2411 fixed Unpredictable, but repeatable VirtualBox crash - WinXP guest, browsing UNC => Fixed in 2.0.4 myxiplx
Description

I have twice had VirtualBox crash in exactly the same way. I'm running a Windows XP Pro guest (SP2), on a Windows 2000 domain, and VirtualBox crashed when I entered a UNC path in the Run box.

The crash appears very intermittent as I can usually do this dozens of times with no problems, but eventually something seems to kill VirtualBox. Unfortunately it's going to be hard to reproduce as the first time it happened after the guest was running for two days, the second time it had been running for nearly four days.

The crash was caused by:

  • click Start
  • click Run
  • Enter a UNC path (the two causing crashes for me were both of the form \machine\c$)
  • Click Go

At this point VirtualBox instantly crashes and I'm left with a blank screen (in Fullscreen mode). Pressing Host+F takes me back to the main VirtualBox GUI, with a grey screen where my WinXP guest should be.

I attempted to do an ACPI shutdown of the guest (just in case it was a GUI issue), but the Virtualbox interface closed immediately when I did that, making me think the guest had in fact crashed completely.

I have the Virtualbox logs from both crashes if they are of any use, and I originally posted this on the forums here: http://forums.virtualbox.org/viewtopic.php?p=41694#41694

I'm running VirtualBox on Ubuntu 8.04 (with all patches to around 1st Oct), and my guest is Windows XP pro SP2.

Ross

#2413 fixed [Linux] Shared Folders to symlink Sasquatch
Description

When creating a Shared Folder to a symbolic link, it will give an error that the path is not obsolute. Pointing it to a normal folder does not give this error.

The reason I want this, is because all my VMs are on an external hard drive. It works just fine when I swap them from my PC to my laptop, and the paths are the same too. Just the Shared Folders are a bit different. Where my internal hard drive is mounted to /data on my laptop, on my PC it's mounted in /media/data with a symlink /data to it.
For now, I will change the mount point on my laptop to /media, creating the same situation as on my PC, but this should be looked at.

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