All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wright <anthony@overnetdata.com>
To: xen-devel@lists.xen.org
Subject: xen/xen vs xen/kvm nesting with pv drivers
Date: Tue, 6 Sep 2016 13:47:14 +0100 (BST)	[thread overview]
Message-ID: <21926294.38.1473166034486.JavaMail.root@zimbra.overnetdata.com> (raw)
In-Reply-To: <27810356.26.1473165229135.JavaMail.root@zimbra.overnetdata.com>

I tried to install Xen (4.7.0 with linux 4.7.2 Dom0) on an AWS virtual machine and it failed because while AWS uses Xen it requires that you use the PVHVM network driver. I then tried to install Xen on a Google Cloud virtual machine and despite also requiring you to use PV drivers, that succeeded because Google Cloud uses KVM.

I think this means that if you nest Xen in KVM you can use high performance drivers, but if you nest Xen in Xen you have to use slower drivers, which seems to be the wrong way around!

I'd like to be able to install Xen on an AWS virtual machine, and wondered what are the challenges to getting the pv drivers working in a nested environment. Is this a problem with the Dom0 kernel only expecting there to be a single XenStore, or is there also a problem in Xen?

Thanks,

Anthony Wright

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

       reply	other threads:[~2016-09-06 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <27810356.26.1473165229135.JavaMail.root@zimbra.overnetdata.com>
2016-09-06 12:47 ` Anthony Wright [this message]
2016-09-06 13:05   ` xen/xen vs xen/kvm nesting with pv drivers Andrew Cooper
2016-09-06 13:32     ` Anthony Wright
2016-09-06 14:36       ` Andrew Cooper
2016-09-06 15:40         ` Konrad Rzeszutek Wilk
2016-09-06 17:31           ` Konrad Rzeszutek Wilk

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=21926294.38.1473166034486.JavaMail.root@zimbra.overnetdata.com \
    --to=anthony@overnetdata.com \
    --cc=xen-devel@lists.xen.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 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.