VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (736 - 738 of 16363)

Ticket Resolution Summary Owner Reporter
#18211 invalid Adding physical DVD drive in FreeBSD causes segfault dbarowy
Description

I have the following two FreeBSD ports installed:

virtualbox-ose-kmod-5.2.22     VirtualBox kernel module for FreeBSD
virtualbox-ose-nox11-5.2.22_1  General-purpose full virtualizer for x86 hardware

I am able to start up and use VirtualBox VMs, mostly without any issues, except when I add a physical drive. If I do the following:

  1. attach an empty DVD drive:
VBoxManage storageattach MyVM --storagectl "SATA Controller" --port 1 --device 0 --type dvddrive --medium emptydrive
  1. then start the VM:
VBoxHeadless --startvm MyVM
  1. then, after the machine boots, connect the VM to the physical DVD drive:
VBoxManage storageattach MyVM --storagectl "SATA Controller" --port 1 --device 0 --type dvddrive --medium host:/dev/cd0

I see the following in my console:

VBoxManage: error: The object functionality is limited
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: "MountMedium(Bstr(pszCtl).raw(), port, device, pMedium2Mount, fForceUnmount)" at line 763 of file VBoxManageStorageController.cpp

And in the console where I have VBoxHeadless running, I see

Segmentation fault

This is confirmed by /var/log/messages on the host, which says:

Dec 20 09:17:00 fbsdhost kernel: pid 77625 (VBoxHeadless), uid 1001: exited on signal 11

The error seems to suggest that there's something goofy with permissions, but whatever it is is not apparent to me (also, a segfault just seems like poor form if this is a valid error). As per FreeBSD instructions, permissions on devices are:

$ ll /dev/cd0 
crw-rw----  1 root  operator  0x56 Dec 12 15:16 /dev/cd0
$ ll /dev/xpt0 
crw-rw----  1 root  operator  0x49 Dec 12 15:16 /dev/xpt0
$ ll /dev/pass*
crw-rw----  1 root  operator  0x50 Dec 12 15:16 /dev/pass0
crw-rw----  1 root  operator  0x51 Dec 12 15:16 /dev/pass1
crw-rw----  1 root  operator  0x52 Dec 12 15:16 /dev/pass2
crw-rw----  1 root  operator  0x53 Dec 12 15:16 /dev/pass3
crw-rw----  1 root  operator  0x54 Dec 12 15:16 /dev/pass4

and my user is in the operator and vboxusers groups.

$ groups
meuser wheel operator vboxusers

I've attached the VBox.log for this machine.

#3418 fixed Addition of GUI/ForceCloseAction extradata item Terry Ellison
Description

See Forum topic graceful shutdown from linux host for the background to this one. The user like a few others in the past have felt that a nice feature to add to the GUI interface would be the ability to force a response avoiding the "Close Virtual Machine" dialogue (typically in the case to savestate). This would simplify logoff and shutdown integration of GUI based VMs running on the desktop. Looking at src/VBox/Frontends/VirtualBox4/src/VBoxConsoleWnd.cpp, this would be a fairly simple change to the logic of VBoxConsoleWnd::closeEvent to add a call to cmachine.GetExtraData for the new parameter and short-circuit logic to bypass display of VBoxCloseVMDlg and process the action immediately.

#6592 duplicate Additional host-only network settings lost after host restart Bruno Girin
Description

When configuring an additional host-only network in VirtualBox, the settings are lost after a restart of the host system (but not after a restart of the VirtualBox application).

Steps to reproduce

  1. Open VirtualBox OSE
  2. Go to File -> Preferences
  3. Select Network
  4. Click on the "Add" button
  5. Configure the new network with DHCP disabled, IPv4: 192.168.57.1, netmask 255.255.255.0, name vboxnet1
  6. Configure a virtual machine to use vboxnet1 for one of its network interfaces
  7. Start the virtual machine: should start normally
  8. Stop the virtual machine
  9. Close Virtual Box
  10. Restart VirtualBox
  11. Start the virtual machine: should start normally again
  12. Stop the virtual machine
  13. Stop Virtual Box
  14. Shutdown and restart the host
  15. Start VirtualBox
  16. Start the virtual machine that uses vboxnet1
  17. The virtual machine fails to start due to a missing network
  18. Go to File -> Preferences
  19. Select Network
  20. vboxnet1 is no longer listed in the network preferences
  21. Open a terminal and type: cat ~/.VirtualBox/VirtualBox.xml
  22. vboxnet1 is listed in the config file even though it does not appear in the GUI

Expected result

In step 17, the virtual machine that uses vboxnet1 should start normally and in step 20 vboxnet1 should be listed in the list of networks.

Actual result

In step 17, the virtual machine that uses vboxnet1 cannot start and in step 20 vboxnet1 is no longer listed in the list of networks and needs to be re-created. Just clicking on the "Add" button seems to do the trick and the network details are populated as they were before: whether this is due to me choosing default values or the GUI actually re-reading the config file for that network, I don't know.

More info

This bug was originally reported on Ubuntu Linux and file on Launchpad as bug 510133.

In addition, I also received an email from a CentOS user who encountered the same problem:

I found your bug report online. I am also experiencing the exact same bug. If you could do me a favor and keep me in the loop on this issue, I would appreciate it. Also, if you have any questions from me as to what I'm running, please ask.


Host
OS: CentOS 5.4
Kernel: 2.6.18-164.11.1.el5

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