VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1069 - 1071 of 16363)

Ticket Resolution Summary Owner Reporter
#9652 obsolete 2D acceleration: video overlay size doesn't change automatically Donuts
Description

Hi,

Host: VirtualBox 4.0.12 on Xubuntu 9.10 x86, Nvidia driver 260.19.29.

I'm using DScaler (http://deinterlace.sourceforge.net/) in a Windows XP SP3 guest. DScaler can use video capture devices to show video in a window on the Windows desktop. It can apply various image-processing methods before displaying.

DScaler uses the overlay feature, so I enabled the VirtualBox 2D acceleration feature. I mostly works correctly, however there is one minor problem.

When the overlay size is changed, the displayed video does not get resized as it should, until I move the DScaler window. As soon as I do that the video shows in the correct size.

To see the problem, run DScaler and start displaying video. Change the deinterlacing method (Deinterlace menu) between e.g. Simple Weave and Old Game. The Old Game deinterlacer uses a half-height overlay (which should occupy the same space on-screen). When you switch to the Old Game deinterlacer, the displayed video is squashed into the upper half of the window, with the previous video content remaining in the bottom half. If you move the DScaler window, this problem corrects itself and the video is stretched to fill the whole window.

Running DScaler natively in Windows (Vista) this problem does not occur.

#9653 obsolete High latency with USB video capture devices Donuts
Description

Host: Xubuntu 9.10 x86. Guest: Windows XP SP3

Hi,

I've been trying to use several USB video capture devices in a Windows XP SP3 guest, e.g. a Pinnacle PCTV USB2 which uses an Empia EM28xx chip.

When used natively in both Linux and Windows, there is very little latency between the input video and what is shown on screen (using e.g. tvtime in Linux or DScaler in Windows). So for example, video games are still very playable.

When used in a VirtualBox guest however, latency is much higher. At least 1-2 seconds, making interactive use with a game console unusable. Is that a defect which could be fixed, or a problem intrinsic to how VirtualBox captures USB devices?

Some other capture devices (e.g. one based on Trident TV Master chip) don't show video at all in the Windows guest; I just got a black window and crackling audio with that. Maybe that's due to the XP driver not working with the increased USB latency?

#9655 fixed Unable to start VM next time if snapshot creation failed in previous session => Fixed in SVN Donuts
Description

Hi,

When snapshot creation fails (e.g. due to lack of disk space), VirtualBox refuses to start the VM next time. That can be worked around by manually editing the .vbox file to remove the reference to the snapshot.

I was using an XP SP3 VM (with VirtualBox 4.0.12, Xubuntu 9.10 x86 host) and selected Take Snapshot... from the menu. That failed because there was not enough disk space. I continued to use the VM and eventually shut it down.

Next time I wanted to start the VM, the VirtualBox Manager showed this message:

Hard disk '/path_to_vdi/vm_name.vdi' with UUID {f2d2f9bd-bf1a-4cbb-ae12-8c279333d908} cannot be directly attached to the virtual machine 'vm_name' ('/path_to_vbox_file/vm_name.vbox') because it has 1 differencing child hard disks.
Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Machine
Interface: 
IMachine {662c175e-a69d-40b8-a77a-1d719d0ab062}

In the VM Snapshots directory, there is a file {aee182d7-b84e-489a-982d-09c0472bdd66}.vdi which is 266,240 bytes long.

Looking at the VBox.log file, there is this text:

00:05:28.449 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
00:05:28.454 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
00:05:32.626 Changing the VM state from 'SUSPENDED' to 'SAVING'.
00:05:33.624 SSM: Giving up: Low on disk space. (cbFree=10465280, SSM_MIN_DISK_FREE=10485760).
00:05:33.624 ssmR3StrmWriteBuffers: Write failed with rc=VERR_SSM_LOW_ON_DISK_SPACE at offStream=0x2e1b7e1
00:05:33.625 SSM: Execute save failed with rc=VERR_SSM_LOW_ON_DISK_SPACE for data unit 'pgm'/#1.
00:05:33.625 VUSB: attached 'aee9feb8[proxy 2304:0208]' to port 1
00:05:33.638 SSM: Failed to save the VM state to '/path_to_vm/vm_name/Snapshots/{4a1ac72d-f024-416b-ac5b-149ab6e5af68}.sav' (file deleted): VERR_SSM_LOW_ON_DISK_SPACE
00:05:33.638 Changing the VM state from 'SAVING' to 'SUSPENDED'.
00:05:33.638 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console} aText={Failed to save the machine state to '/path_to_vm/vm_name/Snapshots/{4a1ac72d-f024-416b-ac5b-149ab6e5af68}.sav' (VERR_SSM_LOW_ON_DISK_SPACE)}, preserve=false
00:05:39.120 Changing the VM state from 'SUSPENDED' to 'RESUMING'.
00:05:39.120 Changing the VM state from 'RESUMING' to 'RUNNING'.

In the .vbox VM file there is this:

        <HardDisk uuid="{f2d2f9bd-bf1a-4cbb-ae12-8c279333d908}" location="/path_to_vdi/vm_name.vdi" format="VDI" type="Normal">
          <HardDisk uuid="{aee182d7-b84e-489a-982d-09c0472bdd66}" location="Snapshots/{aee182d7-b84e-489a-982d-09c0472bdd66}.vdi" format="VDI"/>
        </HardDisk>

After deleting the line referring to the snapshot file, I was able to start the VM normally.

On a snapshot creation error, VirtualBox should remove any reference to the snapshot in the .vbox file (and delete any bogus/useless file in the Snapshots directory I guess).

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