All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Prof. Dr. Michael Schefczyk" <michael@schefczyk.net>,
	Eric Blake <eblake@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] "File too large" error from "qemu-img snapshot" (was Re: AW: Bug Repoting Directions Request)
Date: Mon, 24 Nov 2014 12:52:50 +0100	[thread overview]
Message-ID: <54731C12.3060606@redhat.com> (raw)
In-Reply-To: <2A6E6B95B6E5C146ACE8440760E58185BDC4FF51@EXCHANGESERVER.schefczyk.local>



On 22/11/2014 18:02, Prof. Dr. Michael Schefczyk wrote:
> The further features seem to be reserved to RHEL (and potentially
> other distributions) but not included in Centos:
> 
> virsh snapshot-create-as issues "Live Disk Snapshot not supported in
> this version of QEMU" (retranslated from German).
> 
> virsh blockcommit issues "Online Transfer not supported ..."
> 
> Thus, with Centos 7 it should be possible to back up VMs without
> shutting them down. They are being paused, however, as long as the
> snapshot is created. The qemu-guest-agent does not help in this
> context, as the features which depend on it are not available in
> Centos.

Actually, they are available in most distributions except RHEL and 
CentOS.  For various reasons that I cannot really detail here, Red Hat 
is only shipping these features as part of the "Red Hat Cloud 
Infrastructure" product.

Luckily, since you are using CentOS you do not really care about 
official Red Hat RPMs, and you can get the packages here:

http://resources.ovirt.org/pub/ovirt-3.5/rpm/el7Server/

This yum repository file will help:

    [qemu-kvm-rhev]
    name=oVirt rebuilds of qemu-kvm-rhev
    baseurl=http://resources.ovirt.org/pub/ovirt-3.5/rpm/el7Server/
    mirrorlist=http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-3.5-el7Server
    enabled=1
    skip_if_unavailable=1
    gpgcheck=0

Drop it in /etc/yum.repos.d/qemu-kvm-rhev.repo and install qemu-kvm-rhev
with yum.  All features will be available.  It would be simpler to have
a CentOS SIG build this, but it hasn't happened yet.

Thanks,

Paolo

  reply	other threads:[~2014-11-24 11:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 10:36 Bug Repoting Directions Request Prof. Dr. Michael Schefczyk
2014-11-19 10:59 ` Paolo Bonzini
     [not found]   ` <2A6E6B95B6E5C146ACE8440760E58185BDC31C30@EXCHANGESERVER.schefczyk.local>
2014-11-19 11:41     ` [Qemu-devel] "File too large" error from "qemu-img snapshot" (was Re: AW: Bug Repoting Directions Request) Paolo Bonzini
2014-11-19 11:48       ` Prof. Dr. Michael Schefczyk
2014-11-19 11:53         ` Paolo Bonzini
2014-11-19 12:07           ` Prof. Dr. Michael Schefczyk
2014-11-19 14:54             ` Paolo Bonzini
2014-11-19 15:43               ` Eric Blake
2014-11-19 17:32                 ` Prof. Dr. Michael Schefczyk
2014-11-19 18:13                   ` Eric Blake
2014-11-22 17:02                     ` Prof. Dr. Michael Schefczyk
2014-11-24 11:52                       ` Paolo Bonzini [this message]
2014-11-25 11:34                       ` Kevin Wolf
2014-11-25 11:49                         ` Prof. Dr. Michael Schefczyk
2014-11-24 10:32                     ` Kashyap Chamarthy
2014-11-19 14:05       ` Max Reitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54731C12.3060606@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=eblake@redhat.com \
    --cc=michael@schefczyk.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.