VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1300 - 1302 of 16363)

Ticket Resolution Summary Owner Reporter
#2108 fixed Bogus error message when changing settings on VirtualBox 2.0.0 => fixed in 2.0.2 GabrielVlasiu
Description

After changing some settings for a guest machine (which have a snapshot) and press OK (even if I do not modify anything) an error message is shown:

The snapshot folder of a machine with snapshots cannot be changed (please discard all snapshots first).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component:   Machine
Interface:   IMachine {1e509de4-d96c-4f44-8b94-860194f710ac}

Despite this error, changes are applied to guest.

#11177 fixed Boot Options Changes lost after reboot the VM drh
Description

Hello

OS Host: Win 7 Ultimate 64 bits on Asus M70Vn CPU: C2D Intel T9900 / GPU: nVidia 9650M GT / RAM: 8 GB / Intel VT-x + VT-d OK

OS Guest: Ubuntu 12.04 LTS 64 bits / UEFI / RAM: 1 GB / VBOX HDD: 15 GB

* Problem description: when I set a new option boot in Boot Maintenance Manager => Boot Options => Add New Boot Options for booting my Ubuntu VM UEFI with \EFI\Ubuntu\grubx64.efi path and save the changes, the change is saved and I can boot the Ubuntu VM via Boot Manager => 'the option boot entry newly created'; but, when I reboot the VM, back in Boot Manager, the entry created before has disappeared.

#4394 wontfix Boot Order is not working with gPXE (NIC > CD-ROM > ...) Won Ju Yeon
Description

I've just tried to test gPXE (http://www.etherboot.org) with iSCSI booting features on the VirtualBox.

My Boot Order is the below as you can see it on the log file.

  1. NIC
  2. CD-ROM

My test scenario is the below.

  1. After power on, Intel PXE fetch gPXE by chainloading feature of gPXE in dhcpd.
  2. Then, run it.
  3. gPXE could try to boot a remote disk through iSCSI. But, it would be failed cause of the disk blank.
  4. So, gPXE would hand the boot control over the next boot medium, CD-ROM.
  5. Finally it could be possible to install some OS through iSCSI.

On the above steps, the system is halt on step #3. (See Screenshot-PXE iSCSI Boot [Running] - Sun VirtualBox-01.png)

Therefore, I guess there are some problem on the iSCSI Target side or on the VirtualBox. So, I just skipped the gPXE process. But, the boot process was not normal. (See Screenshot-PXE iSCSI Boot [Running] - Sun VirtualBox-02.png)

I just saw this gPXE is working well on VMWare. (You can see it on YouTube...) I think there are some problem to work with gPXE on the VirtualBox.

God bless you...

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