similar to: use dirty bitmap to backup raw images

Hi, Has anyone met the same problem that virsh hangs when there are some backup jobs running on the kvm host? I use dirty bitmap supported by qemu to do backups every 6 minitues. About a few hours later, I ran 'virsh list', It hung. Then I stopped the backup jobs ?nothing was getting better. I had checked the libvirt logs ?but found nothing useful . Maybe the high I/O caused the

On 08/03/2015 10:47 PM, Martin Kletzander wrote: > On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>> Using: >>> >>> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >>> edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch >>> >>> On Fedora 22. >>> >>> Provisioning

On 08/06/2015 08:08 AM, Martin Kletzander wrote: > On Tue, Aug 04, 2015 at 07:11:29AM -0700, Ryan Barry wrote: >> On 08/03/2015 10:47 PM, Martin Kletzander wrote: >>> On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >>>> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>>>> Using: >>>>> >>>>>

On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: >I'm trying to clone a volume in a storage pool and I'm following the steps >described here: >http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html > >My code looks like: > > destXML = """ >

On Fri, Feb 19, 2016 at 12:33:10PM +0000, Andrei Perietanu wrote: >On Fri, Feb 19, 2016 at 12:12 PM, Martin Kletzander <mkletzan@redhat.com> >wrote: > >> On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: >> >>> I'm trying to clone a volume in a storage pool and I'm following the steps >>> described here: >>> >>>

On Tue, Aug 04, 2015 at 07:11:29AM -0700, Ryan Barry wrote: >On 08/03/2015 10:47 PM, Martin Kletzander wrote: >> On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >>> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>>> Using: >>>> >>>> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >>>>

I'm trying to clone a volume in a storage pool and I'm following the steps described here: http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html My code looks like: destXML = """ <volume>

Hi, I've seen that in the past, libvirt couldn't start VMs when the disk image was stored on a file system that doesn't support direct I/O having the 'cache=none' configuration [0]. On the KubeVirt project, we have some storage tests on a particular provider which does just that - try to create / start a VM whose disk is on tmpfs and whose definition features

On Mon, Dec 16, 2019 at 12:49:40 +0100, Jens John wrote: > Hello list, Hi Jens, > > upon upgrading from libvirt v5.9.0 -> v5.10.0, libvirt started calling > qemu differently causing the VM operating system to not be found. I'm > wondering whether I'm chasing a bug, or have to otherwise fix my domain > config (created by virt-manager). Yes, this change was done by

On Fri, Mar 27, 2020 at 12:31:07PM +0100, Miguel Duarte de Mora Barroso wrote: > Hi, > > I've seen that in the past, libvirt couldn't start VMs when the disk > image was stored on a file system that doesn't support direct I/O > having the 'cache=none' configuration [0]. > > On the KubeVirt project, we have some storage tests on a particular > provider

On 10/15/14, 2:37 AM, Kashyap Chamarthy wrote: > On Tue, Oct 14, 2014 at 02:08:41PM -0600, Eric Blake wrote: >> On 10/14/2014 11:52 AM, Jd wrote: >>> Hi >>> >>> * Trying to get drive-backup command, getting permission denied. :( >>> >>> sudo virsh qemu-monitor-command --hmp my-instance --cmd >>> drive_backup

On Fri, Feb 19, 2016 at 12:12 PM, Martin Kletzander <mkletzan@redhat.com> wrote: > On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: > >> I'm trying to clone a volume in a storage pool and I'm following the steps >> described here: >> >>

Hello list, upon upgrading from libvirt v5.9.0 -> v5.10.0, libvirt started calling qemu differently causing the VM operating system to not be found. I'm wondering whether I'm chasing a bug, or have to otherwise fix my domain config (created by virt-manager). To start with, I have a Windows 7 domain based on the following images: windows7-base.qcow2: QEMU QCOW2 Image (v3),

On 11/17/2013 09:18 PM, Matthew Harrold wrote: > On Sun, Nov 17, 2013 at 7:44 PM, Cole Robinson <crobinso@redhat.com > <mailto:crobinso@redhat.com>> wrote: > On 11/17/2013 01:26 PM, Matthew Harrold wrote: > > Hi All. > > > > I'm trying to setup a guest within my hypervisor that acts as a Console > > Server, using 10 USB

On 10/14/2014 11:52 AM, Jd wrote: > Hi > > * Trying to get drive-backup command, getting permission denied. :( > > sudo virsh qemu-monitor-command --hmp my-instance --cmd > drive_backup drive-virtio-disk0 /tmp/foo.vda.img Ouch. qemu-monitor-command is explicitly unsupported, precisely because it goes behind libvirt's back and is likely to get libvirt confused.

On Tue, Oct 14, 2014 at 02:08:41PM -0600, Eric Blake wrote: > On 10/14/2014 11:52 AM, Jd wrote: > > Hi > > > > * Trying to get drive-backup command, getting permission denied. :( > > > > sudo virsh qemu-monitor-command --hmp my-instance --cmd > > drive_backup drive-virtio-disk0 /tmp/foo.vda.img > > Ouch. qemu-monitor-command is explicitly

Hello. I've been tesing VGA passthrough using libvirt. However, My *Windows7*(64bit) Virtual Machine stopped at loading screen as soon as I installed graphic driver(*AMD Radeon HD 7750*) and then restarted the VM. How Can I use VGA passthrough technology in my *Windows7* VM? I attached my testing information(HW, system environment and settings, qemu log and so on..) Best Regards.

On 02/12/2015 07:41 PM, Edward Young wrote: > Hi all, > > > When I live migrate a vm using > > "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system > tcp://192.168.1.3" > > > I got the following error > > > WARNING: Image format was not specified for > 'nbd://node2:49155/drive-virtio-disk0' and

Dear colleagues, I am facing a problem that has been troubling me for last week and a half. Please if you are able to help or offer some guidance. I have a non-prod POC environment with 2 CentOS7 fully updated hypervisors and an NFS filer that serves as a VM image storage. The overall environment works exceptionally well. However, starting a few weeks ago I have been trying to implement virtlock

Hi all, When I live migrate a vm using "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system tcp://192.168.1.3" I got the following error WARNING: Image format was not specified for 'nbd://node2:49155/drive-virtio-disk0' and probing guessed raw. 258 Automatically detecting the format is dangerous for raw images, write operations on