VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2212 - 2214 of 16363)

Ticket Resolution Summary Owner Reporter
#2138 duplicate Virtualbox 2.0.0 Crashes When Creating New Image (Vista SP1 Host) Mr. Jason R. Hughes
Description

When creating a new .VDI image in a Vista Home Premium SP1 host, I click on the button to begin creating the image. Then the screen turns white and stays that way for a few seconds. The next thing that happens is Windows reports that Virtualbox has crashed. I am trying to create a fixed-size disk image to fit inside a 37.25GB partition, while leaving 1GB of free space on the partition (this is on a PCI card with RAID0 running 2 80GB Maxtor hard drives). I have tried creating the image first on my primary Windows Vista partition and then moving the file over to the partition I intend to use it on, but I get the same error when trying to create the partition. I just upgraded to 2.0.0 yesterday. Before, I was using 1.6.4 and this crash did not happen.

#2139 worksforme Cannot port forward on Virtualbox-2.0 graingert
Description

When attempting to forward port host:2222 to guest:22 I get:

NAT#0: configuration error: failed to set up redirection of 2222 to 10.0.2.15:22. Probably a conflict with existing services or other rules. VBox status code: -3002 (VERR_NAT_REDIR_SETUP).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

This prevents guest from booting!!

#2140 fixed Relax disk image assignment restrictions, please! A20_user
Description

It is ok if a read/write harddisk image cannot be used by two running v.m. at the same time, but it is a very bad idea to prevent assignment of same image to different machines. This hinders tests with different machine configurations badly.

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