similar to: blockcopy, userspace iSCSI support?

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

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

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

On 06/10/2013 01:20 PM, Thomas Stein wrote: > Am 10.06.13 09:07, schrieb Kashyap Chamarthy: >> On 06/09/2013 02:46 PM, Thomas Stein wrote: >>> Hello. >>> >>> I just tried the following: >>> >>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml >>> virsh snapshot-create gentoo-template >>> virsh undefine

On 06/09/2013 02:46 PM, Thomas Stein wrote: > Hello. > > I just tried the following: > > virsh dumpxml --security-info gentoo-template > gentoo-template.xml > virsh snapshot-create gentoo-template > virsh undefine gentoo-template Wait - is that really the command you used after "snapshot-create" ? Because: You cannot undefine a guest with a snapshot without

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>

On 01/16/2015 10:21 AM, Scott Sullivan wrote: > My question is this: > > If you have an ongoing blockcopy (drive-mirror) of a running transient VM, and the VM kernel panics, can you restart the VM without interrupting the ongoing blockcopy? Sadly, this is not yet possible. There is work being done in upstream qemu to add persistent bitmap support, and the libvirt would have to be

On 07/02/2013 06:55 AM, Thomas Stein wrote: > >> virsh dumpxml --security-info dom > dom.xml >> virsh undefine dom > > Hello. > > Someone was talking about this (undefining the VM) would not be > neccessary anymore when qemu-1.5 has been released. Is that true? Undefining the VM will not be necessary after two things happen: 1. qemu supports persistent

Hello, I'm seeking the solution to live storage migration using blockcopy. Previously, the "virsh undefine" is required before blockcopy. https://www.redhat.com/archives/libvirt-users/2015-October/msg00027.html QEMU has "block-dirty-bitmap-*" operations now, are there steps for the live storage migration using blockcopy without undefine? By the way, why's the purpose

Am 10.06.13 10:40, schrieb Kashyap Chamarthy: > On 06/10/2013 01:20 PM, Thomas Stein wrote: >> Am 10.06.13 09:07, schrieb Kashyap Chamarthy: >>> On 06/09/2013 02:46 PM, Thomas Stein wrote: >>>> Hello. >>>> >>>> I just tried the following: >>>> >>>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml

On 12/22/2014 03:27 PM, Gary R Hook wrote: > I am experimenting with the blockcopy command, and after figuring out > how to integrate qemu-nbd, nbd-client and > dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: > > What's the point? Among other uses, live storage migration. Let's say you are running on a cluster, where your VM is running locally but

On Mon, Dec 22, 2014 at 03:50:58PM -0700, Eric Blake wrote: > On 12/22/2014 03:27 PM, Gary R Hook wrote: > > I am experimenting with the blockcopy command, and after figuring out > > how to integrate qemu-nbd, nbd-client and > > dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: > > > > What's the point? > > Among other uses, live

On Thu, Jul 03, 2014 at 12:42:20AM +0530, Kashyap Chamarthy wrote: [. . .] Forgot to note: Before blockcopy, the current block device is snap1.qcow2 (after too, it's the same, since we didn't `--pivot` to the copy. > Now, let's do a live blockcopy (with a '--finish' to graecully finish > the mirroring): > > $ virsh blockcopy --domain testvm2 vda \ >

On 12/23/14 6:17 AM, Kashyap Chamarthy wrote: > On Mon, Dec 22, 2014 at 03:50:58PM -0700, Eric Blake wrote: >> On 12/22/2014 03:27 PM, Gary R Hook wrote: >>> I am experimenting with the blockcopy command, and after figuring out >>> how to integrate qemu-nbd, nbd-client and >>> dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: >>>

On 10/13/2015 09:46 PM, Nathan Shearer wrote: > I have a script that performs a backup with the following steps: > > virsh dumpxml --inactive "$DOMAIN" > "$TMP/${DOMAIN}.xml" && \ > virsh dumpxml --inactive "$DOMAIN" > "$DESTINATION_XML" && \ > virsh undefine "$DOMAIN" && \