All of lore.kernel.org
 help / color / mirror / Atom feed
From: chandrashekar shastri <cshastri@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: libvir-list@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, virt-tools-list@redhat.com
Subject: Re: [Qemu-devel] virsh live migration w/o shared storage fails with error as vm is not running
Date: Tue, 18 Jun 2013 16:30:46 +0530	[thread overview]
Message-ID: <51C03DDE.9090407@linux.vnet.ibm.com> (raw)
In-Reply-To: <51BA3D91.5020405@redhat.com>

On 06/14/2013 03:15 AM, Paolo Bonzini wrote:
> Il 13/06/2013 13:26, chandrashekar shastri ha scritto:
>> On 06/13/2013 02:14 PM, Stefan Hajnoczi wrote:
>>> On Thu, Jun 13, 2013 at 10:31:04AM +0530, chandrashekar shastri wrote:
>>>> We are testing the upstream KVM with :
>>>>
>>>> Kernel, Qemu, Libvirt, Virt-Manager is built from the source (git).
>>>>
>>>> kernel version : 3.9.0+
>>>> qemu version : QEMU emulator version 1.5.0
>>>> libvirt version : 1.0.5
> Please try with libvirt 1.0.5.2.
I pulled the latest libvirt from git to test this and some other issues 
as suggested by commuinty.
But I am stuck and not able to make any progress because libvirt 
compliation is failing with below error:

Sorry for Laszlo, Stefan, Martin, Paolo and others for not following the 
things what they have suggessted.

Below is the error what I am getting when I tried to compile the libvirt:

###############################################################
You may need to use the following Makefile variables when linking.
Use them in <program>_LDADD when linking a program, or
in <library>_a_LDFLAGS or <library>_la_LDFLAGS when linking a library.
   $(GETADDRINFO_LIB)
   $(GETHOSTNAME_LIB)
   $(HOSTENT_LIB)
   $(INET_NTOP_LIB)
   $(INET_PTON_LIB)
   $(LDEXP_LIBM)
   $(LIBSOCKET)
   $(LIB_CLOCK_GETTIME)
   $(LIB_EXECINFO)
   $(LIB_FDATASYNC)
   $(LIB_POLL)
   $(LIB_PTHREAD)
   $(LIB_PTHREAD_SIGMASK)
   $(LIB_SELECT)
   $(LTLIBINTL) when linking with libtool, $(LIBINTL) otherwise
   $(LTLIBTHREAD) when linking with libtool, $(LIBTHREAD) otherwise
   $(PTY_LIB)
   $(SERVENT_LIB)

Don't forget to
   - "include gnulib.mk" from within "gnulib/lib/Makefile.am",
   - "include gnulib.mk" from within "gnulib/tests/Makefile.am",
   - mention "-I gnulib/m4" in ACLOCAL_AMFLAGS in Makefile.am,
   - mention "gnulib/m4/gnulib-cache.m4" in EXTRA_DIST in Makefile.am,
   - invoke gl_EARLY in ./configure.ac, right after AC_PROG_CC,
   - invoke gl_INIT in ./configure.ac.
running: AUTOPOINT=true LIBTOOLIZE=true autoreconf --verbose --install 
--force -I gnulib/m4  --no-recursive
autoreconf: Entering directory `.'
autoreconf: running: true --force
autoreconf: running: aclocal -I m4 -I gnulib/m4 --force -I m4 -I gnulib/m4
autoreconf: configure.ac: tracing
autoreconf: running: true --copy --force
autoreconf: running: /usr/bin/autoconf --include=gnulib/m4 --force
autoreconf: running: /usr/bin/autoheader --include=gnulib/m4 --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:2424: error: required file 'gnulib/lib/Makefile.in' not found
configure.ac:2424: error: required file 'gnulib/tests/Makefile.in' not found
autoreconf: automake failed with exit status: 1

###########################################################################


I didn't face any issue with libvirt 1.0.5. Please let me know if I am 
missing anything here or it is really a bug with "gnulib".

Thanks,
Chandrashekar
>
>>>> virt-install : 0.600.3
>>>>
>>>> I have followed the below steps to test the "Live migration w/o
>>>> shared storage" feature :
>>>>
>>>> 1. Created the qemu-img create -f qcow2 vm.qcow2 12G on the
>>>> destination host which is same as the source.
>>>> 2. Started the guest on the source
>>>> 3. Started the vncdisplay to monitor the guest
>>>> 4. Initiated the migration "virsh migrate --live rhel64-64
>>>> qemu+ssh://9.126.89.202/system --verbose --copy-storage-all"
> I recently found a bug here related to IPv4/IPv6.  I need to understand
> if it is in QEMU or libvirt.
>
> Paolo
>

  reply	other threads:[~2013-06-18 11:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  5:01 [Qemu-devel] virsh live migration w/o shared storage fails with error as vm is not running chandrashekar shastri
2013-06-13  8:44 ` Stefan Hajnoczi
2013-06-13 17:26   ` chandrashekar shastri
2013-06-13 21:45     ` Paolo Bonzini
2013-06-18 11:00       ` chandrashekar shastri [this message]
2013-06-19 11:21       ` chandrashekar shastri
2013-07-05  6:23   ` chandrashekar shastri

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=51C03DDE.9090407@linux.vnet.ibm.com \
    --to=cshastri@linux.vnet.ibm.com \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --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 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.