All of lore.kernel.org
 help / color / mirror / Atom feed
From: Asias He <asias.hejun@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: walimis <walimisdev@gmail.com>,
	Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	Sasha Levin <levinsasha928@gmail.com>,
	Prasad Joshi <prasadjoshi124@gmail.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH 2/2] kvm tools: handle failure of command
Date: Wed, 10 Aug 2011 17:28:11 +0800	[thread overview]
Message-ID: <4E424F2B.80204@gmail.com> (raw)
In-Reply-To: <CAOJsxLGGCy=AGUruJ=2RfG0zYvkAzePt3tk-oXq2fLTM1h-CWw@mail.gmail.com>

On 08/10/2011 02:49 PM, Pekka Enberg wrote:
> On Wed, Aug 10, 2011 at 9:32 AM, walimis <walimisdev@gmail.com> wrote:
>> I used to use tap to enable network for guest os, so that I can mount
>> nfs rootfs. meanwhile, I can access the guest os from host os through the
>> network. For kvm tools, I don't know how to do that through userspace
>> networking. Maybe we need a brief explanation in README.
> 
> Right. I've never used that. Asias is that supported?
> 

I have not tried nfs with our user mode network. But I think walimis can
do it with

	sudo ./kvm --network tap

We need sudo because we need CAP_NET_ADMIN to open /dev/net/tun.

By default, the ip address in host side is:

192.168.33.1/24

In guest side, you need to config a ip address for our guest:

	$ sudo ifconfig eth0 192.168.33.15
	$ sudo route add default gw 192.168.33.1
	$ ping 192.168.33.1

That's it.

If you want to access the real world in guest, try NAT or Bridge the tap
device.



-- 
Best Regards,
Asias He

      reply	other threads:[~2011-08-10  9:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  2:44 [PATCH 1/2] kvm tools: convert callback to int and deal with the return value Liming Wang
2011-08-10  2:44 ` [PATCH 2/2] kvm tools: handle failure of command Liming Wang
2011-08-10  5:02   ` Pekka Enberg
2011-08-10  5:03     ` walimis
2011-08-10  5:30       ` Pekka Enberg
2011-08-10  5:33         ` walimis
2011-08-10  5:53           ` Pekka Enberg
2011-08-10  6:12             ` walimis
2011-08-10  6:35               ` Pekka Enberg
2011-08-10  6:32                 ` walimis
2011-08-10  6:49                   ` Pekka Enberg
2011-08-10  9:28                     ` Asias He [this message]

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=4E424F2B.80204@gmail.com \
    --to=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=prasadjoshi124@gmail.com \
    --cc=walimisdev@gmail.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.