VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2185 - 2187 of 16363)

Ticket Resolution Summary Owner Reporter
#21346 duplicate Missing option "Restore snapshot" when closing VM in VBox 7 LaurentG
Description

When closing a VM, if the 3rd option ("Stop VM") there were (up to v6) a check box allowing to restore the latest snapshot.

This option is VERY useful. But it does not exist any more in V7

This is a HUGE regression. All explanations provided in the forum are FALSE and bad reasons. In particular, the "security concern" (some people are supposed to have restored the latest snapshot and then have lost data) is A LOT MORE SERIOUS with the suggested "workaround" (extradata "GUI/DiscardStateOnPowerOff") that is, contrary to the check box, not visible from user in GUI.

Until this option is restored, I removed Vbox 7 and returned to Vbox 6.1.40

I know very well that this new ticket will be soon closed as "duplicate" of several other ones, but I nevertheless decided to create it to be one more voice claiming that this change is a serious error done by dev team that MUST be repaired !

#2786 fixed Having issues with Debian when AMD-V is turned on (erratum 170 CPU) Lawbayly
Description

After Installing Debian 4.0 r5 on my Windows XP 32bit PC, using VBOX 2.1 When I try and do the initial reboot after the install it crashes with lots of Swap File errors as follows:

swap free: Bad Swap file entry 00c00000

it will then either come up with a Segmentation error or if I'm lucky drop me to a busybox shell.

When I turned off AMD-V (hardware Virtualisation) and it worked fine, I posted this in the forum and according to sandervl, it's an issue with VirtualBox

#11381 fixed VBoxManage GUI improperly changes vmdk file location on OVA import => Fixed in SVN Layer 7
Description

I am using VirtualBox Version 4.1.12_Ubuntu on Ubuntu 12.04 LTS. When attempting to import a RHEL 5.8 virtual appliance OVA, the appliance import wizard will improperly change the path of the VMDK when changing the name of the virtual machine.

To reproduce:

  1. Open VirtualBox Manager GUI
  2. File -> Import Appliance
  3. Choose an OVA file and proceed
  4. Change the "Name" property from "vm" to "teststring"
  5. Observe the "Name property changing properly
  6. Observe the "Virtual Disk Image" path change improperly.

Specifically, VBoxManage GUI appears to do a full substitution for "vm" with "teststring" in the VMDK's path.

I have attached two images which have illustrated the behavior. This is obviously a cosmetic issue, as changing the file path of the VMDK/VDI is trivial to do before completing the import and is the currentworkaround.

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