similar to: zfs + iscsi target + vmware esx server

Hi, are there currently any plans to make an iSCSI target created by setting shareiscsi=on on a zvol bindable to a single interface (setting tpgt or acls)? I can cobble something together with ipfilter, but that doesn''t give me enough granularity to say something like: ''host a can see target 1, host c can see targets 2-9'', etc. Also, am I right in thinking without

Rick McNeal and I have been working on building support for sharing ZVOLs as iSCSI targets directly into ZFS. Below is the proposal I''ll be submitting to PSARC. Comments and suggestions are welcome. Adam ---8<--- iSCSI/ZFS Integration A. Overview The goal of this project is to couple ZFS with the iSCSI target in Solaris specifically to make it as easy to create and export ZVOLs

Just installed Nexenta and I''ve been playing around with zfs. root at hzsilo:/tank# uname -a SunOS hzsilo 5.11 NexentaOS_20070105 i86pc i386 i86pc Solaris root at hzsilo:/tank# zfs list NAME USED AVAIL REFER MOUNTPOINT home 89.5K 219G 32K /export/home tank 330K 1.78T 51.9K /tank tank/iscsi_luns 147K

Does opensolaris iSCSI target support SCSI-3 PGR reservation ? My goal is to use the iSCSI LUN created by [1] or [2] as a quorum device for a 3-node suncluster. [1] zfs set shareiscsi=on <storage-pool/zfs volume name> [2] iscsitadm create target ..... Thanks, -- leon This message posted from opensolaris.org

Hey all, I''m setting up a ZFS based fileserver to use both as a shared network drive and separately to have an iSCSI target to be used as the "Hard disk" of a windows based VM runninf on another machine. I''ve built the machine, installed the OS, created the RAIDZ pool and now have a couple of questions (I''m pretty much new to Solaris by the way but have been

I always used IET on CentOS but I have a quick server to setup to backup some VM's, then migrate to DAS on another server and the easiest way for me will be to accomplish this via iSCSI vmfs stores. I figured I would just use the ini that ships with CentOS but have never used it against ESX, anyone do this and have experiences they care to share? Should it be trivial or are there any non

Hi all, Using "old" way of sharing volumes over iscsi in zfs (zfs set shareiscsi=on) i can see i/o stats per iscsi volume running a command iscsitadm show stats -I 1 volume. However i couldn''t find something similar in new framework,comstar. Probably i''m missing something, so if anyone has some tips please share it :) Thanks in advance, Bruno -------------- next part

Starting from this thread: http://www.opensolaris.org/jive/thread.jspa?messageID=118786&#118786 I would love to have the possibility to set an ISCSI alias when doing an shareiscsi=on on ZFS. This will greatly facilate to identify where an IQN is hosted. the ISCSI alias is defined in rfc 3721 e.g. http://www.apps.ietf.org/rfc/rfc3721.html#sec-2 and the CLI could be something like: zfs set

Hi, I am posting my question to both storage-discuss and zfs-discuss as I am not quite sure what is causing the messages I am receiving. I have recently migrated my zfs volume from b104 to b134 and upgraded it from zfs version 14 to 22. It consist of two zvol''s ''vol01/zvol01'' and ''vol01/zvol02''. During zpool import I am getting a non-zero exit code,

On Wed, Dec 05, 2018 at 09:44:17PM +0530, ROHIT SINGH wrote: >Hi Martin, > >Could you please help me with below issue, I am not sure what’s wrong here. >Please find below code and error snippet. > >Thanks for help. > >Code Snippet: - > >from __future__ import print_function >import sys >import libvirt >SASL_USER = <username> >SASL_PASS =

Hi, I have a zfs root Solaris 10 running on my home server. I created an ISCSI target in the following way: # zfs create -V 1g rpool2/iscsivol Turned on the shareiscsi property # zfs set shareiscsi=on rpool2/iscsivol # zfs list rpool2/iscsivol NAME USED AVAIL REFER MOUNTPOINT rpool2/iscsivol 18K 19.9G 18K

Hi Martin, Could you please point me to any example codes in python present for esx? Suppose, I have to power off and power on esx virtual machine, can i get this code somewhere on python to develop some understanding. Actually, I am not able to find sample code related to esx in python, please point me if any such link available. Appreciate your help !! Thanks. Regards Rohit Singh On Wed,

Thanks a lot Martin for help. Really appreciate it. You’re life saver. I will go through these links and will get back to you in case I need anymore information. Once again, thanks for help. Regards Rohit Singh On Thu, 29 Nov 2018 at 2:34 PM, Martin Kletzander <mkletzan@redhat.com> wrote: > On Wed, Nov 28, 2018 at 10:24:55PM +0530, ROHIT SINGH wrote: > >Hi Martin, > >

Thanks Martin, It’s working now. Could you please help me with role of xml in libvirt api and what if I don’t want use of xml in my code. Please let me know. Thanks for help!! Regards Rohit Singh On Thu, 6 Dec 2018 at 11:24 PM, ROHIT SINGH <rohit.singh0908@gmail.com> wrote: > Thanks Martin for help. I will give it a shot. > > Regards > Rohit Singh > > On Thu, 6 Dec 2018

Fix a bug which would have prevented an SSL certification from ever being verified. --- lib/Sys/VirtV2V/Transfer/ESX.pm | 15 ++++++++------- 1 files changed, 8 insertions(+), 7 deletions(-) diff --git a/lib/Sys/VirtV2V/Transfer/ESX.pm b/lib/Sys/VirtV2V/Transfer/ESX.pm index 1da382a..66ba515 100644 --- a/lib/Sys/VirtV2V/Transfer/ESX.pm +++ b/lib/Sys/VirtV2V/Transfer/ESX.pm @@ -53,7 +53,7 @@

Since fetching storage from ESX was split into separate HEAD and GET requests, the SSL certificate has only been validated on the HEAD request. It should be validated on both. --- lib/Sys/VirtV2V/Transfer/ESX.pm | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/lib/Sys/VirtV2V/Transfer/ESX.pm b/lib/Sys/VirtV2V/Transfer/ESX.pm index f638149..5d6b586 100644 ---

If an ESX guest has a snapshot, the path the libvirt driver gives us will look like: [yellow:storage1] RHEL4-X/RHEL4-X-000003.vmdk instead of: [yellow:storage1] RHEL4-X/RHEL4-X.vmdk The current path mangling code does take this into account. This change makes it use the current mechanism first, but try again after removing a '-\d+' suffix if it gets a 404. Trying twice should make it

Thanks a ton for the reply Matthias. I tried your suggestion but now I got one more message saying: *virsh # connect esx://172.16.73.14/?no_verify=1* *Enter username for 172.16.73.14 [root]: root* *Enter root's password for 172.16.73.14: * *error: Failed to connect to the hypervisor* *error: internal error: curl_easy_perform() returned an error: Unsupported protocol (1) : Protocol https not

To Whom It May concern: I found that the following error is caused by adding a scsi disk to install the os, I remove the scsi disk and the error remove but still report 'out of memory': virsh # dumpxml win2003_122 internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName' virsh # list --all Id Name

To Whom It May Concern: I use virsh windows 0.9.3 to connect an esx server 4.0 with no_verify=1. The Esx server is intel 2 x 3.19 GHZ CPU, 8G memroy and 2 TB hard disk. following is my execute commands and results. virsh -c esx://xxx.xxx.xxx.x?no_verify=1 virsh # list all Id Name State ---------------------------------- 80 win2003_122 running virsh # nodeinfo error: