similar to: (no subject)

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

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'

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

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

I''m experimenting with xen + iscsi, and I founded that under heavy stress domU''s can crash entire system, I''ve reproduced this many many times. My system is like this Software: - iSCSI Enterprise Target v0.4.13 - RedHat AS4 update 4 64bit + Xen 3.0.3-0 Kernel 2.6.16.29 + Open iSCSI v2.0.730 (Initiator) - Bonnie++ v1.03a VM: - Debian 3.1r3 + Open iSCSI v2.0.730

Hi, I made a disk image with CloneZilla from the original physical machine. That image was restored on an iSCSI volume. It isn't booting. I got BSOD. I tried IDE, SATA, SCSI disk type without any success. I tried to using virtio driver and if I use my image+W2k3 install CD+virtio VFD the Windows repair console see the disk and I can use the repair console with my image but the windows not

Thanks for you reply! Firstly, I'm very sorry I forgot introduce the scenarios in my experiments. Supposing a case, I have a virtual machine with two disks. One is mounted as a root partition and the other is data partition and the second disk is an iscsi lun, that is to say, not a local disk or image. Now the result wanted is that creating a snapshot for the root disk but not for the data

try snapshot-create-as like below: virsh snapshot-create-as vm --disk-only --diskspec "vda,snapshot=external" 2013/6/25 cmcc.dylan <dx10years@126.com> > > Hi, everyone, > I have found the API snapshotCreateXML() can create a snapshot for a > virtual machine, and the xml configuration file - snapshot.xml as folllows: > <domainsnapshot> >

On Wed, Sep 16, 2015 at 11:10 PM, Nicholas A. Bellinger <nab at linux-iscsi.org> wrote: > Hi Ming & Co, Hi Nic, > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: >> On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: >> > On Thu, Sep 10, 2015 at 6:48 AM, Ming Lin <mlin at kernel.org> wrote: >> > > These 2 patches added virtio-nvme to

On Wed, Sep 16, 2015 at 11:10 PM, Nicholas A. Bellinger <nab at linux-iscsi.org> wrote: > Hi Ming & Co, Hi Nic, > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: >> On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: >> > On Thu, Sep 10, 2015 at 6:48 AM, Ming Lin <mlin at kernel.org> wrote: >> > > These 2 patches added virtio-nvme to

Hi, Here is the XML file of the my VM: <!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh edit SJ-SIMISPC or other application using the libvirt API. --> <domain type='kvm'> <name>SJ-SIMISPC</name>

Right now, on a virsh blockcopy, I know you can do something like this: # Connect DEST target iscsiadm -m node -p ${DESTINATION}:3260 -T ${VOLNAME} -o new iscsiadm -m node -p ${DESTINATION}:3260 -T ${VOLNAME} --login # Copy to connected iSCSI target virsh blockcopy ${DOMAIN} vda /dev/sdc --raw --bandwidth 300 However I have libiscsi compiled into my QEMU. So I can do this with the monitor

So I have an entry for a USB device ( ID 051d:0002, UPS) I want to use with a given vm client. In that vm client's config file I added something like this: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x051d'/> <product id='0x0002'/> </source> </hostdev>

Hello, As we know, libvirt sanlock support file type storage. I wonder *if it supports network storage.* I tried *iSCSI*, but found it didn't generate any resource file: Version: *qemu-2.10 libvirt-3.9 sanlock-3.5* 1. Set configuration: qemu.conf: *lock_manager = "sanlock"* qemu-sanlock.conf: *auto_disk_leases = 1disk_lease_dir = "/var/lib/libvirt/sanlock"host_id =

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

Hi Looking in to implementing (CBT like) delta backup for KVM. The following looks promising..(last paragraph) http://wiki.qemu.org/Features/Snapshots2 * In the last para, there is a mention of copy the blocks from the disk using dirty-bitmap as reference. How to accomplish this ? block-mirror with bitmap or is there a qemu-img command ? some details would be

On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: > On Thu, 2015-09-17 at 16:31 -0700, Ming Lin wrote: > > On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > > > Hi Ming & Co, > > > > > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > >

On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: > On Thu, 2015-09-17 at 16:31 -0700, Ming Lin wrote: > > On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > > > Hi Ming & Co, > > > > > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi 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 >>> virsh) to an iSCSI target and then boot from the LUNs which