VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (832 - 834 of 16363)

Ticket Resolution Summary Owner Reporter
#5314 fixed All VM's stuck or crash after upgrade to 3.0.10 Andrew
Description

I upgraded from 3.0.8 to 3.0.10 by uninstalling the old version and installing the new one. All three of my VMs (RHEL 5.4, Win Server 03, Win Server 08)will not load after upgrade.

#17507 fixed All iscsi storage is flagged 'Inaccessible' since upgrading to VirtualBox 5.2 series => fixed in SVN/next maintenance Peter Anderson
Description

On Fedora 26 (64-bit) host, since upgrading to 5.2 series, all VM with iscsi storage (hosted by Solaris 11.3) are flagged 'Inaccessible'.

I've tried every 5.2 release, including latest test release 5.2.7-120349, but the issue persists even after the iscsi storage is released/removed/re-attached.

If I roll back to 5.1 series the iscsi storage works perfectly again.

Searches for similar issues at virtualbox.org (and more broader searches have not yielded anything useful as yet) - am finding this quite odd as I'm sure I'm not the only one in the world to be running 5.2 series with a Solaris 11.3 iscsi backend...

Attempts to start a Linux VM with iscsi storage flagged 'Inaccessible' give this message:


Could not open the medium '10.0.0.240|iqn.1986-03.com.sun:f25data|50'.

VD: error VERR_PARSE_ERROR opening image file '10.0.0.240|iqn.1986-03.com.sun:f25data|50' (VERR_PARSE_ERROR).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: MediumWrap Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}


#17365 invalid All machines do not work Memzlord
Description

it says FATAL: No bootable medium found! System halted.

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