similar to: Connect libvirt to iSCSI target

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

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

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

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

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

This hotplug script has been tested with IET and NetBSD iSCSI targets, without authentication. This hotplug script will only work with PV guests not using pygrub. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Ian Campbell <ian.campbell@citrix.com> Cc: Ian Jackson <ian.jackson@citrix.com> --- Changes due to 4.3 release freeze: * We can no longer provide a

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

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 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'm having trouble updating my iscsitarget modules, and it seems to be related to a naming convention mixup? here's the output of the build command: [root at vmhost ~]# rpmbuild --rebuild --sign iscsitarget-0.4.14.96-0.amherst.src.rpm Installing iscsitarget-0.4.14.96-0.amherst.src.rpm error: Failed build dependencies: kernel-devel = 2.6.9-42.0.10.ELlarge is needed by

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

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

[root at vmhost vms]# virsh detach-disk puppet vdb error: No found disk whose source path or target is vdb [root at vmhost vms]# virsh --version 0.10.2 [root at vmhost vms]# This probably was solved already but if not, "No found disk" probably sounds better if it was "No disk found"

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

In trying to find out why my usb passthrough is not working, I decided to edit (virsh edit) the config file for the vm client, removing the following lines <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x051d'/> <product id='0x0002'/> </source> </hostdev>

Trying to start one of my vms, a centos one at that, but am getting the following message: [root@vmhost ~]# virsh start voip --paused error: Failed to start domain voip error: cannot open file '/var/tmp/FreePBX-5.211.65-3-x86_64-Full-1388073872.iso': No such file or directory [root@vmhost ~]# But, virsh dumpxml voip shows no info onto the .iso <disk type='file'

Hello all, I'm having problems using the "samba-tool" tool. From the documentation i've read, the following command 'should' work. Apparently i'm missing something. #### [root at vmhost bin]# pwd /usr/local/samba/bin [root at vmhost bin]# ./samba-tool domain provision --realm=mytest.local --domain=MYTEST --adminpass='welcome' --server-role='dc'

I have a Windows XP vm and would like to know how should I set its cpu so it is seen by the vm as a proper 32bit one. In its xml file, I have <os> <type arch='i686' machine='rhel6.2.0'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> <bootmenu enable='yes'/> </os> And this is the machine I