similar to: Specify a disk image file which is on an iscsi target

Hi, For backing chain that all images are iscsi network disk type , such as iscsi://ip/iqn../0(base image) <-iscsi://ip/iqn../1(active image). Currently, 'qemu-img info --backing-chain' command can display correct backing file info, but after starting guest with the active image in backing chain, it don't include the related <backingStore> element in dumpxml. So,

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" />

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

On Wed, Aug 02, 2017 at 05:47:31PM +0300, Fred Rolland wrote: >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"

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

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 all Question 1: I follow this instruction https://github.com/gluster/gluster-block, I use 2 gluster01 (192.168.101.110), gluster02 (192.168.101.111) and create one gluster volume (block-storage). And use gluster-block to create block storage (block-store/win) [root at gluster01 ~]# gluster-block create block-store/win ha 2 192.168.101.110,192.168.101.111 40GiB IQN:

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 documentation¹ but got stuck at section 12.1.5.4.3. > > 1) > virsh

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Former user of Xen and newbie in kvm/qemu/libvirt stuff, I give it a try on my network ;-) I need to run a VM with iSCSI target attached. I did it this way : 1) Creation of iscsi pool (equa.xml) : <pool type="iscsi"> <name>equalog</name> <source> <host name="10.10.0.1"/> <device

On 2013–12–23 John Ferlan wrote: > 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

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

Hi, I am a libvirt qe, I am testing the function about the new location of disk auth element (as sub-element of the source element) in Backing Chain Management. And I have a questions: When all the backing chain are iscsi network disk type(no matter if the authentication is exist), start the guest , it will only has the top level disk in xml and there are no other backingStore in it. The test

Hi People Using Open iSCSI I have been able to create and mount multiple iSCSI partitions and have them mount at boot. Now I wanted to setup a situation where one of the visible iSCSI partitions mounts at boot and the other is only available if I manually connect to it. This led me to the following command *iscsiadm -m node -T

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

I apologize if this has been covered before. I have not seen a blow-by-blow installation guide for Ubuntu onto an iSCSI target. The install guides I have seen assume that you can make a target visible to all, which is a problem if you want multiple iSCSI installations on the same COMSTAR target. During install Ubuntu generates three random initiators and you have to deal with them to get things

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, 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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, This is my first version of the block-iscsi script. Easy to setup, easy to work with. > #general > name = "skinkie_gentoo_old"; > memory = 256; > > # booting > kernel = "/home/skinkie/xen/boot/gentoo"; > > # virtual harddisk > disk = [