similar to: qemu-img snapshots with backing stores?

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

Hi all, I have a strange problem with qemu img disks allocated in a nfs share on a CentOS 6.4 host. Every time when I try to start a vm this error appears: char device redirected to /dev/pts/1 qemu-kvm: -drive file=/data/vmachines/win2k12adsrv/win2k12vol01.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /data/vmachines/win2k12adsrv/win2k12vol01.img:

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

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>

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

Hi All. I'm trying to setup a guest within my hypervisor that acts as a Console Server, using 10 USB to Serial adapters. The Host is all setup and can access each Serial Port without problems. I have attempted to add the Serial Connections to a Guest, using both Virtual Machine Manager and by editing the .XML file, and I can add up to 4 Serial devices (Including one for console access to the

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

# Ref: http://libguestfs.org/guestfs-performance.1.html Run the below command: $ time guestfish -a /dev/null run NOTE: Discard the first few results, to get a hot cache. (Thanks Rich.) 1/ L0. with L1 running. ---------------------------------------------------------------------- $ for i in {1..10}; do time guestfish -a /dev/null run; done real 0m28.277s user 0m11.028s

hi, Some of you might have seen the email on the centos-devel list, for the rest I just wanted to point out that we've been working on getting opennebula ( http://www.opennebula.org/ ) rpms and contextualised images for opennebula available with a very low barrier to entry for CentOS. The 'win' with OpenNebula is that its easy to install, easy to get going, scales well and mostly

hello mailinglist, on gentoo system with qemu-1.6.1, libvirt 1.1.4, libvirt-glib-0.1.7, virt-manager 0.10.0-r1 when i set on virtual machine "cache=none" in the disk-menu, the machine faults to start with: << Fehler beim Starten der Domain: Interner Fehler: Prozess während der Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: -drive

Hi all, I’m running Xen 4.1 on a couple of NetBSD dom0s and NetBSD’s pkgsrc provides both the xl and xm tools for working with Xen 4.1. I understand that xl is the new way of doing things, but I can’t get it to create my guests the way I want and the main symptom of this is that the text console isn’t available. When I create a guest with xl it starts up qemu-dm (which xm doesn’t do) and I get

On Tue, Apr 12, 2016 at 06:24:16PM -0400, TomK wrote: >On 4/12/2016 5:08 PM, John Ferlan wrote: >> Having/using a root squash via an NFS pool is "easy" (famous last words) >> >> Create some pool XML (taking the example I have) >> >> % cat nfs.xml >> <pool type='netfs'> >> <name>rootsquash</name> >>

Hello, I have cluster with AMD EPYC 7351 cpu. Two CPUs per node. I have performance 8-NUMA configuration: This is from hypervizor: [root@hde10 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 2 Core(s) per socket: 16 Socket(s): 2 NUMA

On 04/13/2016 09:23 AM, TomK wrote: > On 4/13/2016 1:33 AM, Martin Kletzander wrote: >> On Tue, Apr 12, 2016 at 06:24:16PM -0400, TomK wrote: >>> On 4/12/2016 5:08 PM, John Ferlan wrote: >>>> Having/using a root squash via an NFS pool is "easy" (famous last >>>> words) >>>> >>>> Create some pool XML (taking the example I

hello I'm currently using libvirt and opennebula. I have installed the libvirt with the driver of opennebule "ONE" and I test the installation. /********************************************************/ oneadmin at node016 ~]$ virsh -c one:/// Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh

Any error in your host logs? On Sunday, 30 October 2016, Steven Tardy <sjt5atra at gmail.com> wrote: > > > On Oct 30, 2016, at 3:27 AM, Paul R. Ganci <ganci at nurdog.com > <javascript:;>> wrote: > > > > grub> set root=(hd0,msdos2) > > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 > root=(hd0,msdos2)/ > > grub> initrd

On Wed, Jun 22, 2016 at 05:56:09PM -0500, libvirt_users@skagitattic.com wrote: > > Delete what you've done and start from the beginning. Describe > > exactly how you created the guest. Use 'qemu-img info' to show the > > format of the input file. Show precisely the virt-sparsify command > > you are running. And use 'qemu-img info' on the output file

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 Looks like apparmor issue. What can I modify to make this work ? * Couple of other questions drive-backup : * The doc seems to claim that it gives a point in time copy of

Hi, When I'm trying to run qemu-kvm command on RHEL6(linux kernel 2.6.32) then I get following errors which I think related to tap devices in my setup. Any idea why is that? bash$ LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-00000027 -uuid