From: Eric Blake <eblake@redhat.com>
To: chandrashekar shastri <cshastri@linux.vnet.ibm.com>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org,
virt-tools-list@redhat.com
Subject: Re: [Qemu-devel] virsh live migration with non-shared storage fails with error as vm is not running
Date: Thu, 13 Jun 2013 10:30:01 +0100 [thread overview]
Message-ID: <51B99119.1010600@redhat.com> (raw)
In-Reply-To: <51B89213.8090605@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On 06/12/2013 04:21 PM, chandrashekar shastri wrote:
> Hi All,
>
> I have attached the dedug log of libvirt, please let me with your comments.
Spamming 3 separate lists with nearly a megabyte of logs is considered
poor netiquette. It causes lots of server time to multiply that out to
all the recipients, and not every one is able to cheaply download that
much material, especially if they are subscribed to multiple lists.
Your post was moderated and dropped before it hit libvirt, but looks
like it still got through to qemu-devel and virt-tools. Please be more
careful in the future.
--
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: 621 bytes --]
next prev parent reply other threads:[~2013-06-13 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 14:29 [Qemu-devel] Upstream : virt-install and virt-manager fails to install the guest with the error "qemu: could not load PC BIOS 'bios.bin'" chandrashekar shastri
2013-06-12 14:44 ` [Qemu-devel] NMI watchdog issue chandrashekar shastri
2013-06-12 15:21 ` [Qemu-devel] virsh live migration with non-shared storage fails with error as vm is not running chandrashekar shastri
2013-06-13 9:30 ` Eric Blake [this message]
2013-06-13 7:19 ` [Qemu-devel] [libvirt] Upstream : virt-install and virt-manager fails to install the guest with the error "qemu: could not load PC BIOS 'bios.bin'" Martin Kletzander
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=51B99119.1010600@redhat.com \
--to=eblake@redhat.com \
--cc=cshastri@linux.vnet.ibm.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virt-tools-list@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).