similar to: Bug#820154: (no subject)

Package: xen-utils-4.4 Version: 4.4.1-9+deb8u4 Severity: important Dear Maintainer, * What led up to the situation? Upgrading to Debian 8.4. * What exactly did you do (or not do) that was effective (or ineffective)? Doing a live migration to a host running Xen 4.4.1-9+deb8u4, from a host running 4.4.1-9+deb8u3 fails every time. Doing a live migration to a host running Xen

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important I still am not able to create iSCSI storage repositories using this command xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn> device-config:SCSIid=<my-scsi-id>

Package: xen-utils-common Version: 4.0.0-1 Severity: important Xen domains should be shutdown before iSCSI if that is installed. This can be accomplished by adding the following to /etc/init.d/xendomains: # Should-Start: iscsi # Should-Stop: iscsi -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64)

When I use kvm+libvirt as my hypervisor at home, I usually pass logical volumes as the guests' drives (I probably can do better but the disk here is just a garden-variety SSD, not NVMe). <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'

Hi, attached I have some patches which add support for iSCSI LVMoISCSI to the xcp-storage-managers package. The patches are based on the Debian git repository. I have tested my changes and everything seems to work fine. The tests are done on a three node XCP pool with multipath. I haven't tested the changes without multipath. Maybe someone could take a look on the patches and give me some

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

Package: xen-utils-common Version: 4.0.0-1 Severity: important Xen domains should be shutdown before iSCSI if that is installed. This can be accomplished by adding the following to /etc/init.d/xendomains: # Should-Start: iscsi # Should-Stop: iscsi -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64)

Package: xcp-storage-managers Version: 0.1.1-3.1 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem tp crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

Some additional information. I have run an strace of the "xl migrate-receive" process on servers with xen-utils-4.4 4.4.1-9+deb8u4 (which fails) and 4.4.1-9+deb8u3 (which works). On systems with 4.4.1-9+deb8u4 installed, strace shows exactly 395 lines like this one: ioctl(5, SNDCTL_DSP_RESET, 0x7ffeb47b44b0) = -1 EAGAIN (Resource temporarily unavailable) On systems with

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important Dear Maintainer, I can not create an iSCSI storage resource using the following command: xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn>

Hi, I'm trying to build a XCP environment based on wheezy and iSCSI storage. When I try to add a iSCSI SR I get the following error: The SR could not be connected because the driver was not recognised. driver: lvmoiscsi As I couldn't find the driver in /usr/lib/xcp/sm I took a look into the package itself and saw that the driver exists in drivers, but is not listed in the Makefile. Is

Hi there, I have one server acting as a iscsi target running windows storage server r2 sp2 and the other server is running centos as an initiator. They are connected to a switch over a 1Gbit ethernet connection. the target is a Dell NF600 and the server running centos is a Poweredge R900. We want to move this configuration to a FC based installation using a Dell QLE2462 HBA (this is the hba we can

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.

Hi guys, after reading the mailings yesterday i noticed someone was after upgrading to zfs v21 (deduplication) i''m after the same, i installed osol-dev-127 earlier which comes with v19 and then followed the instructions on http://pkg.opensolaris.org/dev/en/index.shtml to bring my system up to date, however, the system is reporting no updates are available and stays at zfs v19, any ideas?

Hi all! I've been experimenting with Xen on CentOS 5 and RHAS 5 for a while now with mixed success I thought I'd describe my latest challenge. I'll describe this from memory since all the equipment is at work and not contactable from here. I think I've described this config to the list before but here it is again: I have 2 x HP DL585 servers each with 4 Dual core Opterons

Hi List, As a ZFS newbie, I foolishly copied my data set to the root zpool file system (a large iSCSI SAN array). Thus: # zpool create -f iscsi c4t19d0 c4t20d0 c4t21d0 c4t22d0 c4t23d0 c4t24d0 # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT iscsi 9.53T 64.5K 5.34T 0% ONLINE - # zfs set mountpoint=/mydisks/iscsi iscsi Then copied

Hi All, I've been trying to figure out the best way of using an iSCSI SAN with KVM and thanks to a helpful post by Tom Georgoulias that I found on this list (https://www.redhat.com/archives/libvirt-users/2010-May/msg00008.html), it appears I have a solution. What I'm wondering is the following: 1) If I use an iSCSI LUN as the storage pool (instead of creating an LVM VG from this iSCSI

I''ve been saving up a few wishlist items for zfs. Time to share. 1. A verbose (-v) option to the zfs commandline. In particular zfs sometimes takes a while to return from zfs snapshot -r tank/volumes at foo in the case where there are a great many iscsi shared volumes underneath. A little progress feedback would go a long way. In general I feel the zfs tools lack sufficient feedback

I have Kronos setup fine. I have installed open-iscsi and setup the system as an initiator. However, I cannot seem to get xapi to allow me to setup the target as an SR. I was trying to use XenCenter but go nowhere. So I tried adding it manually and here is what I got: xe sr-create host-uuid=466aac75-c86a-496f-90e8-2a9925a9e9f7 content-type=user \ > name-label="Shared LVM over iSCSI

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-2 Severity: normal Hi, Take the following config file (standard lenny kernel and initrd, with some customization for iSCSI root): name = "lenny3" kernel = "vmlinuz-2.6.26-2-686-bigmem" ramdisk = "initrd.img-2.6.26-2-686-bigmem" memory = 100 vcpus = 1 vif = [ 'mac=00:16:3e:00:00:17, bridge=br695,