xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xenproject.org
Subject: [TEST] 4.9-rc1 testing results
Date: Mon, 17 Apr 2017 08:49:23 -0400	[thread overview]
Message-ID: <20170417124923.GF28221@char.us.oracle.com> (raw)

Hey,

Over the week I built from scratch and installed Xen 4.9-rc1 on
Fedora Core 20.

I had one issue that I hadn't yet dug completely in - that is the
xenstored.service would not start. Invoking it manually made it
work.

But Fedora Core 20 is ancient, and I am planning to update that machine
to Fedora Core 25 so we can ignore that for now.

In terms of functionality - I am running PV and HVM guests.
The HVM and PV guests are doing PCI passthrough - and it all works!

(The PCI passthrough is via pci=XYZ parameter).

Thanks!

P.S.
SuperMicro X10SAE, E3-1245v3 CPU.

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

                 reply	other threads:[~2017-04-17 12:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170417124923.GF28221@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).