VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (652 - 654 of 16363)

Ticket Resolution Summary Owner Reporter
#10634 obsolete Assert (server_simpleget.c:689) Windows XP when running Premiere Elements with Guest Additions only CarlF
Description

I have a Windows XP Professional guest running on a CentOS 6.2 host, VB version 4.1.16. If and only if the Guest Additions are installed, Adobe Premiere Elements 10 is partially functional (the main preview window doesn't work) and will reliably crash Windows itself (not the application, Windows disappears and VB reports its status as "Aborted") if I try to use certain features, such as double-clicking a clip in the palette in order to preview it.

I tried everything I could think of (turning off hardware acceleration, etc.) and the instability and partial functionality continue.

If I uninstall the Guest Additions, Premiere Elements works perfectly. But the default driver doesn't let me make proper use of my 24" monitor, even in full screen. At the very least, I'd like to be able to keep the mouse driver and network driver that are part of Guest Additions installed, but I can't--you either install all or nothing. This means I can't use shared folders, which is quite annoying. If Oracle can't quickly fix the video driver bug, can you split out the network and mouse drivers from the unusable (for me) video one?

The core dump attached shows a crash caused by double-clicking an item in the media list of Premiere Elements 10.

#13830 duplicate Shared folders are no longer accessible/visible Carlos Castaneda
Description

Since Version 4.3.22 shared folders are no longer accessible nor visible within VBOXSRV in Windows network. This used to work up to version 4.3.20 and when opening VBOXSRV folder there was a list of all defined shared folders.

#15373 duplicate VirtualBox will delete VM settings at startup if DVDImages with conflicting UUIDs exist in VM MediaRegistry -> duplicate of #17908 Carlos D.
Description

This issue frequently deletes a large part of VM settings (namely Display, Storage, Network, USB, Shared Folders) if multiple VMs have conflicting UUIDs of the same DVDImage in their MediaRegistry blocks. The conflicting UUIDs seem to be introduced by BOINC tasks (Distributed Computing using VirtualBox for some projects) that are created and configured automatically. Possibly they don't register their mounted VBOXGuestAdditions.iso correctly, and any later mounting in a regular VM creates a conflicting UUID.

For my test I used a fresh VBox config and created three VMs from scratch: Test1, Test2, Test3. All are created with the default template and settings the Windows VBox offers (Windows 7, default RAM, HDD size etc). Then, for all three VMs, I loaded the VBOXGuestAdditions.iso to their virtual DVD drive, then ejected it immediately. That created the entry in their MediaRegistry.

      <DVDImages>
        <Image uuid="{8c2aa2b9-4628-401d-88dc-707d8825017f}" location="C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso"/>
      </DVDImages>

All three have the same UUID for the ISO, so anything is fine. Only for quickly recreating the issue, I now manually modified the UUID of the Test1 VM to another, valid one. I know that it should never happen, but unfortunately it does.

      <DVDImages>
        <Image uuid="{707d8825-401d-88dc-4628-017f8c2aa2b9}" location="C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso"/>
      </DVDImages>

The next start of VirtualBox deleted the settings of Test2 and Test3.

Attached are some screenshots, the vbox files and the VBoxSVC.log.

Notes:

  1. There is no VM VBox.log, since none of the VMs are ever started.
  2. VBoxGuestAdditions.iso is only an example, every ISO works.
  3. The VMs having Harddisks attached is a requirement. Without Harddisks the VMs become inaccessible (which I think is correct behavior).
  4. All VMs and config files are on local HDDs and accessible at all times. No configs are ever moved.
  5. While the VirtualBox.xml file has a MediaRegistry block, nothing was ever registered there.

As for the solution, while the correct solution would be to display the "Inaccessible" message for conflicting VMs, that would probably break BOINC tasks, frequently. So, would it be possible to simply update the wrong UUIDs to the right one, if the complete path to the ISO is the same? Because it is the very same ISO, then.

I hope that's enough information to recreate.

Backlink to original forum topic: https://forums.virtualbox.org/viewtopic.php?f=6&t=77399

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