similar to: iSCSI and disk timeouts

Hi, I have set up a 40GB iscsi target on my san and when I add it in to the storage pool and it shows up as 40GB. When I try to create a 40GB volume in the ovirt UI it tries to but fails. The error message is that the volume will not fit. If I create one smaller than 40GB it works. Is anyone else experiencing this? Also, if I then start a virtual machine up to install on the newly

Hi, When I click on "Edit Network" on my managed node in the hosts tab of the oVirt UI I only see one NIC. My managed node has 2 NICs, one on the guest network and one on the admin network. The NIC on the admin network is not listed in the network editor. Is this normal? I'm trying to create a VM and boot the cobbler profile I created for Fedora 10 but I can only boot the VM

I''m just wondering if anyone has tried this, and what the performance has been like. Scenario: I''ve got a bunch of v20z machines, with 2 disks. One has the OS on it, and the other is free. As these are disposable client machines, I''m not going to mirror the OS disk. I have a disk server with a striped mirror zpool, carved into a bunch of zvols, each exported via

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

Two questions (and then a bonus one), kind of interrelated, but, first, some basic info. I'm using OCFS2 on OpenSUSE 10.2, kernel 2.6.18.8(-0.7). There are three nodes in the OCFS2 cluster, backed by Openfiler iSCSI storage. First, I'm using Openfiler and iSCSI volumes to back my OCFS2 file system. The nodes that are part of the OCFS2 cluster use the file system as a shared storage

This add an iscsi initiator name setup option to the main menu in ovirt-config-setup and can also be accessed via ovirt-config-iscsi. Also accepts AUTO setup by running ovirt-config-iscsi AUTO and generates a random name as before --- Makefile.am | 1 + ovirt-node.spec.in | 3 ++ scripts/ovirt-config-boot | 4 --- scripts/ovirt-config-iscsi | 56

Hi there, during peak load on some running domU, I noticed random iSCSI "Reported LUNs data has changed" which forced me to shutdown the respective domU, re-login the target and do a fsck before starting domU again. This occurred on a 16 core machine, having only about 14 domUs running. Spare memory has been occupied by dom0 (about 40G). Each domU has it''s own iSCSI target.

The VMs just boot up with the default network interface model which is 100Mb, is there a way to set it to a 1Gb model? Cheers, Justin.

This enables the ability to take the ovirt-node-image iso and deploy it to an iscsi disk. It also provides a sample pxe configuration for booting based on the iscsi root device. Includes support for user/password as well as reverse chap user/password. --- Makefile.am | 1 + livecd-iso-to-iscsi | 201 ++++++++++++++++++++++++++++++++++++++++++++++ ovirt-node-image.spec.in |

I am currently going through the process of installing/configuring an iSCSI target and cannot find a good write up on how to prepare the disks on the server. I would like to mirror the two disks and present them to the client. Mirroring isn't the question, its how I go about it is the problem. When I partitioned the two drives and mirrored them together, then presented them to the client,

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

Has anyone tried using glusterfs to handle live sysvol replication? Cheers, Justin.

Hello all, I got some severe iscsi connection loss on my dom0 (Gentoo 2.6.20-xen-r6, xen 3.1.1). Happening several times a day. open-iscsi version is 2.0.865.12. Target iscsi is the open-e DSS product. Here is a snip of my messages log file: May 5 16:52:50 ying connection226:0: iscsi: detected conn error (1011) May 5 16:52:51 ying iscsid: connect failed (111) May 5 16:52:51 ying iscsid:

Just started messing with multipath against an iSCSI target with 4 nics. What should one expect as behavior when paths start failing? My lab setup was copying some data on a mounted block device when I dropped 3 of 4 paths and the responsiveness of the server completely tanked for several minutes. Is that still expected? Thanks, jlc

Hello, thanks for the help. Yes And the commands to discovery iscsi results ok Such iscsiadm --mode discovery --type sendtargets And scsiadm -m node -T And the disks appear on pvdisplay 2018-03-14 16:23 GMT-03:00 Marcelo Roccasalva < marcelo-centos at irrigacion.gov.ar>: > On Wed, Mar 14, 2018 at 4:08 PM, marcos sr <msr.mailing at gmail.com> wrote: > > > >

I''ve recently upgraded my x4500 to Nevada build 97, and am having problems with the iscsi target. Background: this box is used to serve NFS underlying a VMware ESX environment (zfs filesystem-type datasets) and presents iSCSI targets (zfs zvol datasets) for a Windows host and to act as zoneroots for Solaris 10 hosts. For optimal random-read performance, I''ve configured a single

Hello All, I am running NTFS over iSCSI on a ZFS ZVOL volume with compression=gzip-9 and blocksize=8K. The server is 2 core P4 3.0 Ghz with 5 GB of RAM. Whenever I start copying files from Windows onto the ZFS disk, after about 100-200 Mb been copied the server starts to experience freezes. I have iostat running, which freezes as well. Even pings on both of the network adapters are reporting

- dracut does not currently support booting a dmsquash file system on an iscsiroot - can not be configured in standalone mode since networking is not up, although works fine if ovirt-config-setup is run once booted. Signed-off-by: Joey Boggs <jboggs at redhat.com> --- recipe/common-pkgs.ks | 1 + scripts/ovirt-config-boot | 67 ++++++++++++++++----

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