public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: David Evensky <evensky@dancer.ca.sandia.gov>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	kvm@vger.kernel.org, mingo@elte.hu, asias.hejun@gmail.com,
	gorcunov@gmail.com
Subject: Re: [PATCH] kvm tools: Allow remapping guest TTY into host PTS
Date: Thu, 15 Sep 2011 20:09:04 +0300	[thread overview]
Message-ID: <1316106544.3743.25.camel@lappy> (raw)
In-Reply-To: <20110915165239.GB5114@dancer.ca.sandia.gov>

On Thu, 2011-09-15 at 09:52 -0700, David Evensky wrote:
> Sasha,
> 
> So far so good! I applied your patch to an older version of kvm-tool
> that I had hacked on and it works for a simple test. So I think that I
> can do some kernel hacking with kvm tool! Very cool.
> 

Awesome!

> I'm tested with the older version of kvm-tool because I am seeing a
> bug with an old kernel (2.6.28.10) and the latest version of kvm-tool.
> It is an old kernel, and now that I can debug more easily; hopefully I
> won't require it.
> 
> In case this is worthwhile the error I'm seeing is below. While I do
> have 9p compiled into my kernel, I'm not actually using it. I haven't
> tried without the 9p compiled in.
> 

[snip]

> For this kernel, CONFIG_NET_9P_VIRTIO is defined, but the kernel is old, so
> there may be issues.
> 
> \dae
> 

I've noticed that 9p/virtio-9p is a bit unstable in older versions, for
example: you can't use 9p rootfs with kernels older than 2.6.38 (which
isn't that old really).

-- 

Sasha.


  reply	other threads:[~2011-09-15 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15  8:53 [PATCH] kvm tools: Allow remapping guest TTY into host PTS Sasha Levin
2011-09-15  9:32 ` Pekka Enberg
2011-09-15 12:28   ` Sasha Levin
2011-09-15 16:52     ` David Evensky
2011-09-15 17:09       ` Sasha Levin [this message]
2011-09-16  2:22 ` Asias He
2011-09-18 14:30 ` Hagen Paul Pfeifer

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=1316106544.3743.25.camel@lappy \
    --to=levinsasha928@gmail.com \
    --cc=asias.hejun@gmail.com \
    --cc=evensky@dancer.ca.sandia.gov \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /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