Hello, I?ve got VDI 3.2.1 and I?m experiencing ZFS iscsi persistence after rebooting the ZFS Solaris 10 (s9/10 s10x_u9wos_14a X86) server so I tried to use NexentaOS_134f as according to http://sun.systemnews.com/articles/145/5/Virtualization/22991, VDI 3.1.1 supports COMSTAR However, with nexenta, I?m getting the following message after selecting the ZFS pool when trying to add the nexenta ZFS server to VDI 3.2.1: ?A required package (SUNWiscsir) is missing on the storage server? root at vdi02:~# pkginfo | grep iscsi base SUNWiscsiu Sun iSCSI Management Utilities (usr) base SUNWiscsir Sun iSCSI Device Driver (root) base SUNWiscsitr Sun iSCSI COMSTAR Port Provider (root) base SUNWiscsitu Sun iSCSI COMSTAR Port Provider base SUNWiscsidmr Sun iSCSI Data Mover (Root) base SUNWiscsidmu Sun iSCSI Data Mover (Usr) root at vdi02:~# dpkg -l | grep iscsi ii sunwiscsidmr 5.11.134-12 Sun iSCSI Data Mover (Root) ii sunwiscsidmu 5.11.134-12 Sun iSCSI Data Mover (Usr) ii sunwiscsir 5.11.134-12 Sun iSCSI Device Driver (root) ii sunwiscsitr 5.11.134-12a Sun iSCSI COMSTAR Port Provider (root) ii sunwiscsitu 5.11.134-12 Sun iSCSI COMSTAR Port Provider ii sunwiscsiu 5.11.134-12 Sun iSCSI Management Utilities (usr) Am?I missing something ? Cheers, Thierry. -- The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW, UK. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20110130/77e0aca1/attachment.html>
I''m not personally familiar with with VDI, but it feels like the VDI bits are trying to run pkginfo on a NexentaStor target, which is a syntax error. I''m not sure what the fix for that would be. - Garrett On Sun, 2011-01-30 at 09:37 +0000, Thierry Delaitre wrote:> Hello, > > I?ve got VDI 3.2.1 and I?m experiencing ZFS iscsi persistence after > rebooting the ZFS Solaris 10 (s9/10 s10x_u9wos_14a X86) server so I > tried to use NexentaOS_134f as according > to http://sun.systemnews.com/articles/145/5/Virtualization/22991, VDI > 3.1.1 supports COMSTAR > > However, with nexenta, I?m getting the following message after > selecting the ZFS pool when trying to add the nexenta ZFS server to > VDI 3.2.1: > > ?A required package (SUNWiscsir) is missing on the storage server? > > root at vdi02:~# pkginfo | grep iscsi > base SUNWiscsiu Sun iSCSI Management Utilities > (usr) > base SUNWiscsir Sun iSCSI Device Driver (root) > base SUNWiscsitr Sun iSCSI COMSTAR Port Provider > (root) > base SUNWiscsitu Sun iSCSI COMSTAR Port Provider > base SUNWiscsidmr Sun iSCSI Data Mover (Root) > base SUNWiscsidmu Sun iSCSI Data Mover (Usr) > > root at vdi02:~# dpkg -l | grep iscsi > ii sunwiscsidmr 5.11.134-12 > Sun iSCSI Data Mover (Root) > ii sunwiscsidmu 5.11.134-12 > Sun iSCSI Data Mover (Usr) > ii sunwiscsir 5.11.134-12 > Sun iSCSI Device Driver (root) > ii sunwiscsitr 5.11.134-12a > Sun iSCSI COMSTAR Port Provider (root) > ii sunwiscsitu 5.11.134-12 > Sun iSCSI COMSTAR Port Provider > ii sunwiscsiu 5.11.134-12 > Sun iSCSI Management Utilities (usr) > > Am?I missing something ? > > Cheers, > > Thierry. > The University of Westminster is a charity and a company > limited by guarantee. Registration number: 977818 England. > Registered Office: 309 Regent Street, London W1B 2UW. > > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Jan 30, 2011, at 1:37 AM, Thierry Delaitre wrote:> Hello, > > I?ve got VDI 3.2.1 and I?m experiencing ZFS iscsi persistence after rebooting the ZFS Solaris 10 (s9/10 s10x_u9wos_14a X86) server so I tried to use NexentaOS_134f as according > to http://sun.systemnews.com/articles/145/5/Virtualization/22991, VDI 3.1.1 supports COMSTAR > > However, with nexenta, I?m getting the following message after selecting the ZFS pool when trying to add the nexenta ZFS server to VDI 3.2.1: > > ?A required package (SUNWiscsir) is missing on the storage server? > > root at vdi02:~# pkginfo | grep iscsi > base SUNWiscsiu Sun iSCSI Management Utilities (usr) > base SUNWiscsir Sun iSCSI Device Driver (root) > base SUNWiscsitr Sun iSCSI COMSTAR Port Provider (root) > base SUNWiscsitu Sun iSCSI COMSTAR Port Provider > base SUNWiscsidmr Sun iSCSI Data Mover (Root) > base SUNWiscsidmu Sun iSCSI Data Mover (Usr) > > root at vdi02:~# dpkg -l | grep iscsi > ii sunwiscsidmr 5.11.134-12 Sun iSCSI Data Mover (Root) > ii sunwiscsidmu 5.11.134-12 Sun iSCSI Data Mover (Usr) > ii sunwiscsir 5.11.134-12 Sun iSCSI Device Driver (root) > ii sunwiscsitr 5.11.134-12a Sun iSCSI COMSTAR Port Provider (root) > ii sunwiscsitu 5.11.134-12 Sun iSCSI COMSTAR Port Provider > ii sunwiscsiu 5.11.134-12 Sun iSCSI Management Utilities (usr) > > Am?I missing something ?Yes. Solaris 10 does not have COMSTAR (the new iSCSI target software) and NexentaStor 3 does not have the legacy iscsi target. A similar transition occurs when moving from NexentaStor 2 to NexentaStor 3. See the migration FAQ for details. http://support.nexenta.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=140 -- richard -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20110130/99031b4e/attachment.html>
Would you recommend a particular distribution to implement a persistent iscsi server compatible with VDI ? Thierry. From: Richard Elling [mailto:richard.elling at gmail.com] Sent: 30 January 2011 16:28 To: Thierry Delaitre Cc: zfs-discuss at opensolaris.org Subject: Re: [zfs-discuss] VDI, ZFS and comstar On Jan 30, 2011, at 1:37 AM, Thierry Delaitre wrote: Hello, I''ve got VDI 3.2.1 and I''m experiencing ZFS iscsi persistence after rebooting the ZFS Solaris 10 (s9/10 s10x_u9wos_14a X86) server so I tried to use NexentaOS_134f as according to http://sun.systemnews.com/articles/145/5/Virtualization/22991, VDI 3.1.1 supports COMSTAR However, with nexenta, I''m getting the following message after selecting the ZFS pool when trying to add the nexenta ZFS server to VDI 3.2.1: "A required package (SUNWiscsir) is missing on the storage server" root at vdi02:~# pkginfo | grep iscsi base SUNWiscsiu Sun iSCSI Management Utilities (usr) base SUNWiscsir Sun iSCSI Device Driver (root) base SUNWiscsitr Sun iSCSI COMSTAR Port Provider (root) base SUNWiscsitu Sun iSCSI COMSTAR Port Provider base SUNWiscsidmr Sun iSCSI Data Mover (Root) base SUNWiscsidmu Sun iSCSI Data Mover (Usr) root at vdi02:~# dpkg -l | grep iscsi ii sunwiscsidmr 5.11.134-12 Sun iSCSI Data Mover (Root) ii sunwiscsidmu 5.11.134-12 Sun iSCSI Data Mover (Usr) ii sunwiscsir 5.11.134-12 Sun iSCSI Device Driver (root) ii sunwiscsitr 5.11.134-12a Sun iSCSI COMSTAR Port Provider (root) ii sunwiscsitu 5.11.134-12 Sun iSCSI COMSTAR Port Provider ii sunwiscsiu 5.11.134-12 Sun iSCSI Management Utilities (usr) Am''I missing something ? Yes. Solaris 10 does not have COMSTAR (the new iSCSI target software) and NexentaStor 3 does not have the legacy iscsi target. A similar transition occurs when moving from NexentaStor 2 to NexentaStor 3. See the migration FAQ for details. http://support.nexenta.com/index.php?_m=knowledgebase&_a=viewarticle&kba rticleid=140 -- richard -- The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW, UK. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20110130/7a3dbb1f/attachment-0001.html>
On Jan 30, 2011, at 11:08 AM, Thierry Delaitre wrote:> Would you recommend a particular distribution to implement a persistent iscsi server compatible with VDI ?Of course, I will recommend NexentaStor! :-) But I would also recommend NFS over iSCSI, but that is fodder for another forum... -- richard -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20110130/2b44a34b/attachment.html>