similar to: why attach-disk can't be effective when the guest is booting

Hi, I'm trying to create a snapshot on a specific disk by using diskspec option. However, libvirt/virsh seems to ignore it and takes a snapshot of all disks. Am I using this option incorrectly? In below examples, I'm trying to snapshot only vdb. However even vda is getting snapshotted regardless of diskspec. Is this a known issue? I'm on CentOS 7.1, libvirtd (libvirt) 1.2.8, virsh

I'm unable to detach a disk from a Windows guest using the 'virsh detach-disk' command. Even though 'domblklist' shows the disk attached, and on the FIRST iteration, it says the command "completed successfully," 'domblklist will still show the disk attached and subsequent 'detach-disk' commands fail with 'no disk found whose source path or target

Hello, I did a virsh snapshot-create-as --domain meta sn1 --diskspec vda,file=/var/lib/libvirt/images/meta-sn1.qcow2 --disk-only --atomic --no-metadata Then I successfully blockcommitted 2 disks: virsh blockcommit meta vda --active --verbose --pivot virsh blockcommit meta vdb --active --verbose --pivot But when doing virsh blockcommit meta vdc --active --verbose --pivot I got: Block commit:

Hello Fairly new to libvirt. I’m hoping to both solve a problem with this question as well as learn more detail about how libvirt works. Using RHEL 6.4 and libvirt version is 0.10.2 and qemu-img version is 0.12.1.2 Using virt-manager I created a VM. Nothing unusual as far as I can see. I then added a disk. So I have a second virtio based volume which the guest then mounts as a separate

Hi! I was reading the Wiki about 'Live Disk Backup with Active Blockcommit, https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit and see that example shown seems to be using two different names for the same file. First showing the current block device in use: $ virsh domblklist vm1 Target Source ------------------------------------------------ vda

Hello Thanks heaps for your suggestions. responses inline. On 10 Apr 2014, at 10:34 pm, Eric Blake <eblake@rehost1hat.com> wrote: > > [ … ] > [Can you convince your mailer to wrap long lines? It makes it easier > for other readers] I’ll try and keep the lines short. I don’t see any obvious setting to change the wrap. >> >> Using RHEL 6.4 and libvirt version

Thank you for your help! 1, i used vda as install disk and vdb as target disk, because i boot from the first. After setup boot order flag i was able change install disk to vdb and target disk to vda. With this configuration when i boot from vdb i can install OS with grub and after it redefine XML without vdb without problem. Thanks a lot. 2, maybe i have something wrong, but still not working:

On 08/07/2015 09:53 AM, Silver Sky Soft Services, Inc. wrote: > Hi, > I'm trying to create a snapshot on a specific disk by using diskspec > option. However, libvirt/virsh seems to ignore it and takes a snapshot of > all disks. Am I using this option incorrectly? > > In below examples, I'm trying to snapshot only vdb. However even vda is > getting snapshotted

Hi All. I have a dell system with a H700 raid. Within the hardware RAID config I've created a "virtual disk" which I have assigned to one of my guests. On the host the device is "/dev/sdb", on the guest it's "/dev/vdb". This works fine. Within the guest, we have created lvm PV on /dev/vdb (using the whole disk - no partitions) and created a volume

Hi Team, I am doing a small testing and I don't know if my expectation is correct or not. Pardon me if I am ignorant. I created a VM and the VM is running. In the hypervisor I have created ".img" file and attached this .img file to the VM. My expectation is that, if VM is writing files to the attached disk, then it should reflect in the .img file created in the hypervisor. But It is

Greetings, list! I hope you forgive cross-posting - I only now found this list. I am in the process of configuring a KVM stack of about 8 vms. Mostly I am concerned about performance, as there will be a lot of I/O. My last problem is this: I try to add a fresh, unformatted disk partition to a KVM guest. I follow the directions given here:

Dear all, Please let me start by indicating that I am not from a technical background, so please be gentle and patient with me. I am trying to get a snapshot from my virtual machines (vm) and the following command works for all of them bar one: # virsh snapshot-create-as --quiesce --no-metadata --domain myvm myvm-state --diskspec vda,file=overlay.qcow2 --disk-only --atomic The only exception is

REPRODUCIBLE EXAMPLE: With the R.rsp package installed, the following search, which gives a hit: options(help_type = "html") help.search("rsp") generates: Error in if (nchar(Outfile)) Outfile else File : argument is not interpretable as logical in the browser (e.g. http://127.0.0.1:30410/doc/html/Search?results=1). Another example is

Hi, dear friend. My guest has two disks, vda and vdb. both are qcow2 local file. When guest running state. I want to take the vda snapshot of guest(just vda, no include vdb). but I met libvirt do snapshot for all disks of guest. About methods for follow: 1、 ``` bash virsh snapshot-create-as 8x0lbzvS --name sys_disk3 --disk-only --diskspec "vda,snapshot=external" ``` ``` result

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

Greets, I am unsure if it's a linux- or libvirt-issue: I added a 2nd virtio-disk to a kvm-based VM. The xml shows a correct "target": # first disk vda <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/r0/vm1_vda-clone.img'/> <target dev='vda'

Hi, I am adding a disk to my KVM virtual server, but for some reason it refuses to honor the <address> I have tried the following 3: <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/nbd2'/> <target dev='vdb' bus='virtio'/>

I take an internal snapshot (VM is 'shutdown' when taking it) of a qcow2 image like this: $ qemu-img snapshot -c sn1 [my_image].qcow2 I see that snapshot when asking for: $ qemu-img info [my_image].qcow but do NOT see it with: $ virsh domblklist [my_domain] is that how it is meant to be?

hi,all I use Java api `domain.attachDeviceFlags(xml, 0);` to add a disk for domain. the xml file like this: <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/dev/sp1353486595267/v1353488096262'/> <target dev='vdb' bus='virtio'/> </disk> then I use command