VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (331 - 333 of 16363)

Ticket Resolution Summary Owner Reporter
#192 wontfix OpenBSD reports full disk on install (requires VT-x or AMD-V; unsupported with software virtualization) scy
Description

OpenBSD (3.9) aborts the installation process reporting a full disk.

uid 0 on /: file system full

/: write failed, file system is full

I've tried static and dynamic images, and there is also much free space on the file system of the host os.

Tested with VirtualBox 1.3.6 and 1.3.8

#193 fixed create vdi file from physical disk michel0000
Description

It would be great if it would be possible to create a vdi file from a physical disk. For example, like that you can create a vdi file from your C: drive, mount it on a new virtualbox and start your pc a second time within virtual box and do tests on it, before doing these on the real machine.

#194 fixed "Failed to initialize COM ... VirtualBox COM server" error message after re-boot, first login pablo
Description

Hi,

For more information, see the '[vbox-users]' list: March 14 around noon ET.

Subject: openSUSE 10.2 - "Failed to initialize COM ... VirtualBox COM server" error

It appears we have a regression. In 1.3.6, openSUSE 10.2/KDE, I am able to leave the main VirtualBox window running and reboot my machine and at first login, there are no VirtualBox errors.

With 1.3.8 and the same environment, I get the above error message in a pop-up box at first login after a reboot.

In 1.3.6 and 1.3.8, I see two processes running after I shut down VirtualBox:

  • VBoxSVC --daemonize
  • VBoxXPCOMIPCD

If I manually 'kill' the processes in 1.3.8 before rebooting my machine, no error is displayed.

In 1.3.6, I don't have to 'kill' these processes.

Cheers, -pablo

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