All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Hu, Robert" <robert.hu@intel.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d
Date: Fri, 27 Jun 2014 11:32:25 +0200	[thread overview]
Message-ID: <1403861545.5251.12.camel@Solace> (raw)
In-Reply-To: <9E79D1C9A97CFD4097BCE431828FDD3197BEFA@SHSMSX103.ccr.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1599 bytes --]

On ven, 2014-06-27 at 03:57 +0000, Hu, Robert wrote:
> Hi All,
> This is a report based on our testing for Xen 4.5-unstable on Intel platforms.
> 
> Test environment:
> Xen: Xen 4.5-unstable with qemu-upstream-unstable.git git commit: f7e46156a1c006a6eb5489e0227d39229eec316d
> Dom0: Linux kernel 3.15.1
> Hardware: Intel Ivy Bridge, Haswell Bridge
> 
> New bug (1): 
> 1. When trying onboard I350 NIC as VT-d, the device cannot get IP in guest
>   http://bugzilla-archived.xenproject.org/bugzilla/show_bug.cgi?id=1889
> 
One thing I'm wondering is whether we can 'convert' these very cool and
useful reports to use our official bug tracking system, instead of the
archived bugzilla one.

It's very convenient anyway, since you already put the links, etc., but
I think it would be way better to have only one place where to look at,
and that should be bugs.xenproject.org!

Some info about it and about how to use it are available here:
 http://bugs.xenproject.org/xen/
 http://wiki.xen.org/wiki/Xen_Bug_Management_Interface
 http://lists.xen.org/archives/html/xen-users/2013-05/msg00556.html

Since he's the author, IanC is the guy if you need more info, but I
think you can just ask question about it here in the mailing list, I'm
sure someone will be able to help you. :-)

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  parent reply	other threads:[~2014-06-27  9:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27  3:57 VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d Hu, Robert
2014-06-27  8:43 ` Jan Beulich
2014-07-24  7:56   ` Jan Beulich
2014-06-27  9:32 ` Dario Faggioli [this message]
2014-07-01  6:36   ` Hu, Robert
2014-07-01  7:57     ` Ian Campbell

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=1403861545.5251.12.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=robert.hu@intel.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.