VirtualBox

Ticket #5935 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

OpenSolaris iSCSI boot client panic - can't read pool label

Reported by: wmsch Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 3.1.2 Keywords:
Cc: Guest type: Solaris
Host type: Solaris

Description

OpenSolaris panics using VirtualBox iSCSI initiator to boot.

Steps:

  • OpenSolaris is installed to an iSCSI target using the OpenSolaris initiator
  • The vbox is shut down
  • The disk that was previously declared with "VBoxManage addiscsi ..." is added to the vbox.\
  • The vbox is rebooted.
  • GRUB menu appears,
  • Boot proceeds briefly, but kernel panics because it can't read the ZFS pool label.

From console: NOTICE: Can not read the pool label from '/iscsi_vhci/disk/g6000<hex string>b00:a NOTICE: spa_import_rootpool: error 5 Cannot mount root on /iscsi_vhci/disk/g000<hex string>b00:a fstype zfs panic in vfs_mountroot - see attached screenshot

Wireshark ethernet trace does not show any errors, but one Inquiry Response Data message says [iSCSI transfer limited due to allocation_length too small] Trace available upon request.

Log attached

Networking: bridged e1000g

NOTE: The OpenSolaris iSCSI boot install has just been pushed to the repository and is not yet fully publicly documented. Do not hesitate to contact me with any questions or concerns.

Attachments

cantreadpoollabel.log Download (42.5 KB) - added by wmsch 4 years ago.
VirtualBox log
cantreadpoollabel.png Download (30.6 KB) - added by wmsch 4 years ago.
Screenshot of OpenSolaris console
menu.lst.png Download (122.5 KB) - added by wmsch 4 years ago.
Screenshot of menu.lst

Change History

Changed 4 years ago by wmsch

Changed 4 years ago by wmsch

Screenshot of OpenSolaris console

comment:1 Changed 4 years ago by wmsch

Tested boot of the same iSCSI boot target using hardware with iSCSI NIC - booted without panic.

Changed 4 years ago by wmsch

Screenshot of menu.lst

comment:2 Changed 4 years ago by wmsch

Hand-typed GRUB commands - boot archive appears to be read.

As a test, did a complete install to the iSCSI boot target through the VirtualBox initiator - the installation finished without reporting any problems.

comment:3 Changed 4 years ago by klaus

  • Status changed from new to closed
  • Resolution set to invalid

This seems to be a misunderstanding, as the behavior looks perfectly normal.

The VirtualBox iSCSI initiator is not seen by the guest as iSCSI, it is seen as a regular IDE/SATA/SCSI disk. This means that you have to adjust your Solaris boot config accordingly. The panic will not go away ss long as it expects to see an iSCSI NIC and boot off it. VirtualBox doesn't have such a thing, it completely hides iSCSI.

There are lots of "change disk controller" recipes out there for Solaris, one of them is  http://blogs.sun.com/jimlaurent/entry/importing_solaris_vmdk_image_into (which probably needs quite some adjustments for OpenSolaris).

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use