From: Eric Blake <eblake@redhat.com>
To: Puneet Bakshi <bakshi.puneet@gmail.com>,
libvir-list@redhat.com, qemu-devel@nongnu.org,
qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] [libvirt] Where to get precompiled qga-vss.dll from ?
Date: Mon, 07 Jul 2014 15:57:22 -0600 [thread overview]
Message-ID: <53BB17C2.1090400@redhat.com> (raw)
In-Reply-To: <CALBPQ33-HUBmV3EFdfSQkkL79Dg80-du0kKv42LWHEk1F18vwg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On 07/07/2014 02:32 AM, Puneet Bakshi wrote:
> Hi,
>
> I want to work with "guest-fsfreeze-*" commands in Windows 2008 guest VM.
> Host is CentOS 6.4.
>
> Windows 2008 is running QEMU VSS provider. When "guest-fsfreeze-*" commands
> are invoked from host, response received is "This is not supported".
>
> I am following
> http://lists.gnu.org/archive/html/qemu-devel/2013-02/msg01963.html.
The libvirt list is the wrong place to be asking this question; qemu is
better.
The spice-devel list has done some pre-packaged virt stack builds for
Windows; maybe they might be a better resource to ask (for example, see
http://lists.freedesktop.org/archives/spice-devel/2014-February/016100.html)
- but I don't follow that list closely enough to know if they have
pre-built qga.
You could always download the mingw cross-compiler and try to build qga
yourself, instead of relying on someone else to provide a pre-built binary.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-07-07 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 8:32 [Qemu-devel] Where to get precompiled qga-vss.dll from ? Puneet Bakshi
2014-07-07 21:57 ` Eric Blake [this message]
2014-07-08 5:12 ` [Qemu-devel] [libvirt] " Puneet Bakshi
2014-07-08 19:46 ` Tomoki Sekiyama
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=53BB17C2.1090400@redhat.com \
--to=eblake@redhat.com \
--cc=bakshi.puneet@gmail.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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.