Custom Query (16363 matches)
Results (2344 - 2346 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4326 | fixed | Failed to start VM with iSCSI disk (VERR_NO_DIGITS) => fixed in svn | ||
| Description |
I have created an VM with an iSCSI disk attached. The disk is accessible: $ VBoxManage list hdds VirtualBox Command Line Management Interface Version 3.0.0 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. UUID: db119233-9eb9-4560-a349-fb3fb468108d Format: iSCSI Location: 192.168.10.1|iqn.1994-04.org.netbsd.iscsi-target:target0 Accessible: yes Usage: w_xp (UUID: 6559588e-d090-4ec6-8878-64eed543260b) However, the VM fails to start. Error is: iSCSI: configuration error: failed to convert LUN to integer (VERR_NO_DIGITS). see also attached VBox.log at the very end. This iSCSI Disk used to work with 3.0.0_BETA2_49051 but stopped working with final 3.0.0_49315. Just to verify, i did downgrade to BETA2 an the disk worked again, but after upgrade to final 3.0 it will fail anew. |
|||
| #4327 | fixed | Remove Floppy (in GUI and in Guest) | ||
| Description |
Is there any use of floppy in a VM? If the Floppy option is not checked in the Settings of the VM, in the guest the Floppy device must not exist. Using VirtualBox 3.0.49315 (release). Host = WinXP, Guest = Win2003 x32, newest Guest Additions installed. In the VM settings, Floppy is unchecked. In the Guest, Windows Explorer shows Floppy A: in the left pane. |
|||
| #4328 | fixed | Virtual machine hangs on startup if VT-x enabled | ||
| Description |
In VirtualBox 3.0.0 virtual machine hangs on startup if VT-x is enabled in Processor Options. Even BIOS fade-in/fade-out sequence is not shown, just some garbage in frame-buffer. If I turn off VT-x, machine starts OK. VT-x setting worked fine in previous versions of VirtualBox, namely 2.2.4, 2.2.0, etc. Hardware: Dual Intel(R) Xeon(R) CPU E5450, 32 GB RAM Os: Solaris 10 05/09 |
|||

