VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (76 - 78 of 16363)

Ticket Resolution Summary Owner Reporter
#21288 duplicate "Restore current snapshot" option removed pozzeur
Description

Previously when closing a live VM there was a "Restore current snapshot" option. With 7.x that option has been removed completely, now requiring closing the VM then independently restoring the snapshot. This means more steps to achieve the same result, and more steps means a higher likelihood of things being missed, simple mistakes/forgetting to do one step.

I understand that the reason for this change seems to be due to the persistence of that option being selected has caused users to lose data, unintentionally restoring a snapshot. I believe outright removing the feature is the wrong approach.

Can there be an option to control it's persistence? Something like; by default it's always unchecked, but you can have that option remember either globally or per VM via a separate preference?

#12146 wontfix "Running VirtualBox in a Xen environment is not supported" on "3.2.0-31-generic" knightsamar
Description

My uname -a output is

Linux machine.domain.com 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

And when I do sudo /etc/init.d/vboxdrv setup the output is:

 * Stopping VirtualBox kernel modules                                                                                  [ OK ] 
 * Removing old VirtualBox pci kernel module                                                                           [ OK ] 
 * Removing old VirtualBox netadp kernel module                                                                        [ OK ] 
 * Removing old VirtualBox netflt kernel module                                                                        [ OK ] 
 * Removing old VirtualBox kernel module                                                                               [ OK ] 
 * Recompiling VirtualBox kernel modules                                                                               [ OK ] 
 * Starting VirtualBox kernel modules                                                                                         
 * Running VirtualBox in a Xen environment is not supported

But, running modprobe vboxdrv seems to fix the problem as as lsmod lists the module and I can use VirtualBox.

Attaching the vbox-install.log from /var/log.

#18048 fixed "SUPLIB not initiated successfully" with --disable-hardening --build-debug ==> fixed in SVN Cake
Description

In VirtualBox-5.2.18/src/VBox/VMM/VMMR3/VM.cpp

  • Line 212 calls VMR3GlobalInit, which eventually ends up calling suplibOsIOCtl.
  • Line 238 calls SUPR3Init, which is too late.

The VM starts when I call SUPR3Init(NULL) earlier. I attached a patch, but I assume you will know how to fix it better.

I see someone else has experienced this issue before: https://forums.virtualbox.org/viewtopic.php?f=10&t=84300

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