Oracle VM for SPARC - control/io domain dilemna


 
Thread Tools Search this Thread
Operating Systems Solaris Oracle VM for SPARC - control/io domain dilemna
Prev   Next
# 1  
Old 03-27-2017
Oracle VM for SPARC - control/io domain dilemna

Hi all,

My internal SAS disks (4 of them) are all sitting on the same controller/pcie device which is now being own by my default primary aka io aka control domain.

I have created a vdisk server, that serves slices on these 4 disks to guest domain and everything is working fine.

The issue is that, whenever I need to patch my control domain (reboot) the guest domain will be affected due to the fact that the entire IO/PCIE device is own by primary.

/SYS/MBU/SASHBA PCIE PCIE0 primary OCC

==================

q1) Does this means that I have no way to create another separate IO domain so that whenever I patch my control domain, my guests wont be affected ?

q2) If I have another 2 PCIE device (hba cards connected to SAN), can I assign them to another IO domain, then from that new IO domain, create a vds service and serve disks to guest domains instead ? (come to think of it .. this IO domain need its OS to run, unless I am doing SANBOOT, else this IO domain will still run from vdisk allocated from control)

q3) if a guest domain has no dependencies on the control domain, will patching the primary/control domain cause guests domain to go down ?

Regards,
Noob
 
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

IPMP in the Service Domain (Oracle VM Sparc)

Hello Using VM server 3.1, I would like to configure a vswitch based on IPMP of 2 physical port so that IPMP is only configured on the primary domain and no more on guest domains. Regarding the documentation (Configuring IPMP in a Logical Domains Environment - Oracle VM Server for SPARC 3.0... (10 Replies)
Discussion started by: yguilloux
10 Replies

2. UNIX for Advanced & Expert Users

Recommended Domain/Hosting Control Panels?

Looking for a recommendation - I'm looking for a reliable domain control panel (like cPanel) that is open source, and I can customize it do work into my work flow. Essentially, I need new users to be able to create a new account so that a) a new subdomain is created, or b) a full domain... (0 Replies)
Discussion started by: kettlewell
0 Replies

3. Solaris

Assigning cryptographic resources to the control domain

Sun documentation suggests that we need to assign cryptographic resources to the control domain as part of the initial configuration. I searched the documentation to better understand the purpose of this and know recommendation/limitation. I am doing this for Netra T5220 and wondering if the... (5 Replies)
Discussion started by: StarSol
5 Replies
Login or Register to Ask a Question
MFI(4)							   BSD Kernel Interfaces Manual 						    MFI(4)

NAME
mfi -- LSI MegaRAID SAS driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device pci device mfi Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): mfi_load="YES" DESCRIPTION
This driver is for LSI's next generation PCI Express SAS RAID controllers. Access to RAID arrays (logical disks) from this driver is pro- vided via /dev/mfid? device nodes. A simple management interface is also provided on a per-controller basis via the /dev/mfi? device node. The mfi name is derived from the phrase "MegaRAID Firmware Interface", which is substantially different than the old "MegaRAID" interface and thus requires a new driver. Older SCSI and SATA MegaRAID cards are supported by amr(4) and will not work with this driver. Two sysctls are provided to tune the mfi driver's behavior when a request is made to remove a mounted volume. By default the driver will disallow any requests to remove a mounted volume. If the sysctl dev.mfi.%d.delete_busy_volumes is set to 1, then the driver will allow mounted volumes to be removed. HARDWARE
The mfi driver supports the following hardware: o LSI MegaRAID SAS 1078 o LSI MegaRAID SAS 8408E o LSI MegaRAID SAS 8480E o LSI MegaRAID SAS 9260 o Dell PERC5 o Dell PERC6 o IBM ServeRAID M5015 SAS/SATA o IBM ServeRAID-MR10i o Intel RAID Controller SROMBSAS18E FILES
/dev/mfid? array/logical disk interface /dev/mfi? management interface DIAGNOSTICS
mfid%d: Unable to delete busy device An attempt was made to remove a mounted volume. SEE ALSO
amr(4), pci(4), mfiutil(8) HISTORY
The mfi driver first appeared in FreeBSD 6.1. AUTHORS
The mfi driver and this manual page were written by Scott Long <scottl@FreeBSD.org>. BUGS
The driver does not support big-endian architectures at this time. BSD
May 12, 2010 BSD