VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1543 - 1545 of 16363)

Ticket Resolution Summary Owner Reporter
#8602 obsolete Visual Studio 2010 (Express and other editions) didn't repaint when Direct3D support installed Roman Pushkov
Description

After installing guest additions with experimental Direct3D support Visual Studio 2010 (all editions) didn't repaint after start. Nothing can be done with Studio (can't open files, edit files and build code). Only non-client area (without menu, status bar etc.) shown.

#8615 obsolete Damage to .vbox file for first VM renders all VMs inacessible and VM Manager empty Chris Jenkins
Description

I have 4 VMs con figured. They are all configured similarly to the attached .vbox file.

I had a situation where for unexplained reasons (subject of much discussion but no conclusion as yet) the .vbox file for the first VM that I had defined becamed 'damaged'. By this I mean that three of the 'HardDisk' entries in the 'MediaRegistry' section were removed. The relevant entries for these disks were still present in the 'AttachedDevice' section at the end of the file.

When I opened the VBox GUI, all 4 VMs were shown as 'inacessible', even though there was no problem with the .vbox files for the other three VMs, and when I opened the Virtual Media Manager that also showed as 'empty' (i.e. no media was listed).

I have performed some experiments and have confirmed the following:

  1. This behaviour only happens when the .vbox file for the first defined VM

is 'damaged'. It seems this VM is somehow 'special' from the perspective of its Media Registry?

  1. This behaviour happens consistently when I deliberately 'damage' the .vbox file

for the first VM. Removing just one 'HardDisk' entry that is specific to that VM renders all VMs inaccessible and the VMM 'empty'.

This behaviour isn't very nice. A problem with the .vbox file for the first defined VM should not have any impact on other VMs nor on the Virtual Media Manager.

#8616 obsolete HDD with more than one child Christian
Description

The VM is a win7 x64 and the guest also. Several time when using it and after some tests in the guest i switch it off (like power switch). After this a retun to the last snapshot, so all should be liek before. But sometimes it happens that when i start VB the message came up, that the HDD has moe then one childs. In this case i delete one of them in VM Manager and then in the IDE also the Snapshop (which coukd not be deletetd because of two existing chields).

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