From: Sasha Levin <levinsasha928@gmail.com>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: "penberg@kernel.org" <penberg@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvm tools: ignore nonexisting custom stage2
Date: Wed, 21 Dec 2011 12:11:00 +0200 [thread overview]
Message-ID: <1324462260.3914.0.camel@lappy> (raw)
In-Reply-To: <4EF1ABA5.4050402@openvz.org>
On Wed, 2011-12-21 at 13:49 +0400, Konstantin Khlebnikov wrote:
> Sasha Levin wrote:
> > On Wed, 2011-12-21 at 13:15 +0300, Konstantin Khlebnikov wrote:
> >> fix permanent failing with message "Fatal: Failed linking stage 2 of init."
> >> if there is no custom init_stage2.
> >
> > Why would it happen? whats the usecase?
> >
>
> run "lkvm run" in dir there is no "guest" subdirectory
Yup, but how would that happen? 'guest' is part of the git tree and the
makefile builds the executables in it.
--
Sasha.
next prev parent reply other threads:[~2011-12-21 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 10:15 [PATCH] kvm tools: ignore nonexisting custom stage2 Konstantin Khlebnikov
2011-12-21 9:46 ` Sasha Levin
2011-12-21 9:49 ` Konstantin Khlebnikov
2011-12-21 10:11 ` Sasha Levin [this message]
2011-12-21 10:15 ` Konstantin Khlebnikov
2011-12-21 10:18 ` Sasha Levin
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=1324462260.3914.0.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=khlebnikov@openvz.org \
--cc=kvm@vger.kernel.org \
--cc=penberg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox