similar to: [PATCH] hotplug/Linux: add iscsi block hotplug script

Hi, I'm trying to disconnect some iSCSI targets, but can't seem to. [root at localhost ~]# iscsiadm -m session tcp: [1] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:500gb tcp: [3] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba tcp: [4] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:extent0 tcp: [5] 192.168.2.200:3260,1

Are folks in the Centos community succesfully using device-mapper-multipath? I am looking to deploy it for error handling on our iSCSI setup but there seems to be little traffic about this package on the Centos forums, as far as I can tell, and there seems to be a number of small issues based on my reading the dm-multipath developer lists and related resources. -geoff Geoff Galitz Blankenheim

On 2013–12–21 John Ferlan wrote: > On 12/17/2013 07:13 PM, Marco wrote: > > Hi! > > > > I'm new to libvirt and face problems connecting to an iSCSI target. > > What I intend to do is to connect libvirt (I tried virt-manager and > > virsh) to an iSCSI target and then boot from the LUNs which contain > > the VMs. > > > > I followed the

Hi all, After finding multiples answers to this question via google, but without making it work on my servers. Has anybody iSCSI Offload working on a Dell Server with Broadcom NICs ? My environment: I'm running CentOS 5.6 CR, on a Dell PowerEdge R710 with Broadcom Corporation NetXtreme II BCM5709 conecting to an EMC CX4-120 SAN, via 2x Cisco 2960G-24TC-L switches. It's working

Hello Experts, When I try to create SR with lvm over iSCSI, it always failed, I list my xe command and debug info: [root@xcp16 log]# xe sr-create host-uuid=a226200e-f7ff-4dee-b679-e5f114d1e465 content-type=user name-label=shared_disk_sr shared=true device-config:target=192.168.1.2 device-config:targetIQN=iqn.2013-07.example:shareddisk device-config:SCSIid=1IET_00010001 type=lvmoiscsi The SR is

Hi! I'm new to libvirt and face problems connecting to an iSCSI target. What I intend to do is to connect libvirt (I tried virt-manager and virsh) to an iSCSI target and then boot from the LUNs which contain the VMs. I followed the documentation¹ but got stuck at section 12.1.5.4.3. 1) virsh pool-define-as \ --name foo \ --type iscsi

Hello, I have a small Xen farm of 8 dom0 servers with 64 virtual machines running para-virtualized and this has been working great. Unfortunately, I''ve hit a limit: my iSCSI hardware supports only 512 concurrent connections and so I''m pretty much at the limit. (Wish I would have seen that problem sooner!) Of course, 87% of those connections are idle-- but necessary because I

Hello We were attempting to use scsi-target-utils, hosted on a xen dom0 vm using localhost, and running into some problems. I was not able to reproduce this on a centos 7.2 server using the default kernel. (From dmesg) Apr 4 11:18:42 funk kernel: [ 596.511204] connection2:0: detected conn error (1022) Apr 4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs expired, recv

Hi, i have a debian Etch x86_64 with a xen 3.1 on a kernel 2.6.18-xen. I have some DomU with Debian Etch. I installed open-iscsi, configure /etc/iscsi/iscsid.conf: --- node.active_cnx = 1 node.startup = automatic #node.session.auth.username = dima #node.session.auth.password = aloha node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 10

I am confused, because I would have expected a 1-to-1 mapping, if you create an iscsi target on some system, you would have to specify which LUN it connects to. But that is not the case... I read the man pages for sbdadm, stmfadm, itadm, and iscsiadm. I read some online examples, where you first "sbdadm create-lu" which gives you a GUID for a specific device in the system, and then

By natively, I take it using kernel /vmlinuz (vs kernel /xen) Not yet, but working on setting up such an environment. (At this time, I was using virt-install to reproduce the problem, and the original server we are testing on did not support kvm but the 2nd server does). On 2016-04-12 03:26 AM, George Dunlap wrote: > On Mon, Apr 11, 2016 at 9:14 PM, Nathan Coulson <nathan at

Where can I find a list of supported multipath drivers for ZFS? Keith McAndrew Senior Systems Engineer Northern California SUN Microsystems - Data Management Group <mailto:Keith.McAndrew at SUN.com> Keith.McAndrew at SUN.com 916 715 8352 Cell CONFIDENTIALITY NOTICE The information contained in this transmission may contain privileged and confidential information of SUN

Package: xcp-storage-managers Version: 0.1.1-3 Severity: normal XCP cannot use iscsi block devices. Fails with iscsiadm: No active sessions. I ran the following commands trying to diagnose the problem: First introducing a SR and then creating a PBD with the needed configuration for the iscsi block device. These steps work fine but when I tried to plug the PBD I got the error: root at

Hi List, I don''t know if this is something that is a simple matter of opinion or if there are strong reasons to take one route or the other. I have dom0 nodes with dedicated bond interfaces that connect to a storage traffic-only VLAN. Currently I have a few domUs running that have large-ish volumes on the iSCSI SAN, and to present the volumes I''m connecting the dom0s to the

Hi, I could not find any option to set iSCSI initiator iqn while using guestfish, although the underlying qemu command has this option. It appears that each time guestfish tries to connect to iSCSI LUN, a randomly generated initiator iqn is being used. This is preventing guestfish to connect to the iSCSI target in our environment as the target allows incoming connection based on the preconfigured

On 12/22/2013 10:09 AM, Marco wrote: > On 2013–12–21 John Ferlan wrote: > >> On 12/17/2013 07:13 PM, Marco wrote: >>> Hi! >>> >>> I'm new to libvirt and face problems connecting to an iSCSI target. >>> What I intend to do is to connect libvirt (I tried virt-manager and >>> virsh) to an iSCSI target and then boot from the LUNs which

We''re currently evaluating ZFS prior to (hopefully) rolling it out across our server room, and have managed to lock up a server after connecting to an iSCSI target, and then changing the IP address of the target. Basically we have two test Solaris servers running, and I followed the instructions on the post below to share a zpool on Server1 using the iSCSI Target, and then import that

I've configured a libvirt storage pool using an iscsi target from a Sun 7310 storage appliance and am using the LUNs in this target as volumes for my KVM guests. The setup is very similar to what Daniel covered in a recent blog posting: http://berrange.com/posts/2010/05/05/provisioning-kvm-virtual-machines-on-iscsi-the-hard-way-part-2-of-2/ It works great, but I can't figure out how

Hi Bootmeisters, I am using gpxelinux.0 + sanboot.c32 to boot a diskless machine into Linux. I would like to use device-mapper-multipath to provide fault tolerant access to its root disk. Although I am able to do this by hardcoding the additional paths in the initrd, it would be better if the bootloader could pass the information in the iBFT (iSCSI Boot Firmware Table). However, at the

Hi, I am working on oVirt, and I am trying to run a VM with a network disk with ISCSI protocol ( the storage is on a Cinder server). Here is the disk XML I use: <disk device="disk" snapshot="no" type="network"> <address bus="0" controller="0" target="0" type="drive" unit="0" />