I think the more important question is why would you need to do something in both the control/service domain and the guest domain to the same disk at the same time?
Once you've virtualized the disk as a vdsdev and then attached it as a vdisk, why do you need to touch the disk in the control/service domain? *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Virtualization Architect and Consultant Web: http://unixconsole.blogspot.com E-Mail: unixconsole at yahoo.com *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ----- Original Message ---- From: Rushi Srinivas <[email protected]> To: ldoms-discuss at opensolaris.org Sent: Wednesday, February 18, 2009 10:58:31 PM Subject: Re: [ldoms-discuss] SVM metaset and SCSI commands on vdisk backends Let me explain my question in detail: (1) I have exported a SCSI disk (lun) from control domain to Guest domain. /dev/dsk/c2t5d0s2 (control domain) => /dev/dsk/c0d7 (guest domain) (2) Now, in guest domain I add this device (/dev/dsk/c0d7) to SVM metaset. (3) To know the target infomartion (of the LUN) from control/service domain, I do scsi ioctl on /dev/dsk/c2t5d0s2 (control domain device). I will just use SCSI inquiry command and NOT the reservation commands. (4) Similarly, to know the target information of the same disk from guest domain, I do ioctl SCSI on the guest device (/dev/dsk/c0d7). Also, applications like, VxDMP, SVM metaset may be issuing scsi commands to the guest device. Now, if steps (3) and (4) are carried out at the same time, will my disk go into unexpected state. The only SCSI command I issue is "inquiry" (no reservation commands). -- This message posted from opensolaris.org _______________________________________________ ldoms-discuss mailing list ldoms-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
