VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d

VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d

[Hu, Robert]

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

Verified bugs (2):
1. Dom0 cannot be shutdown before PCI device detachment from guest
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1826
2. Booting multiple guests will lead Dom0 call trace
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1853

Old bugs (4):
1. [XL]"xl vcpu-set" causes dom0 crash or panic
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1730
2. [upstream qemu] Guest free memory with upstream qemu is 14MB lower than that with qemu-xen-unstable.git
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1836
3. sometimes failed to online cpu in Dom0
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1851
4. Failed to create a nested L2 guest based XEN on XEN
  http://bugzilla-archived.xenproject.org//bugzilla/show_bug.cgi?id=1887

Best Regards
Robert Ho

Re: VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d

[Jan Beulich]

>>> On 27.06.14 at 05:57, <robert.hu@intel.com> wrote:
> 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 

I see that you already bisected this - thanks a lot. However, since
that change works fine for me, I'm not going to be able to debug this
myself and hence depend somewhat on someone on your end helping
with this. A first step should in any case be to try Andrew's tools side
fix 0c615f8dadb4389048d574abd1515861d3f8403f on top of the
offending one, which got committed only subsequent to the commit
you tested.

Jan

Re: VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d

[Jan Beulich]

>>> On 27.06.14 at 10:43, <JBeulich@suse.com> wrote:
>>>> On 27.06.14 at 05:57, <robert.hu@intel.com> wrote:
>> 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 
> 
> I see that you already bisected this - thanks a lot. However, since
> that change works fine for me, I'm not going to be able to debug this
> myself and hence depend somewhat on someone on your end helping
> with this. A first step should in any case be to try Andrew's tools side
> fix 0c615f8dadb4389048d574abd1515861d3f8403f on top of the
> offending one, which got committed only subsequent to the commit
> you tested.

Any progress here? We're not going to be able to deal with this
without your help.

Jan

Re: VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d

[Dario Faggioli]

[-- 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

Re: VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d

[Hu, Robert]

> -----Original Message-----
> From: Dario Faggioli [mailto:dario.faggioli@citrix.com]
> Sent: Friday, June 27, 2014 5:32 PM
> To: Hu, Robert
> Cc: xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VMX test report for Xen 4.5-unstable-git
> commit:f7e46156a1c006a6eb5489e0227d39229eec316d
> 
> 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.
> 
Hi Dario, I've just read the http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen,
 "Although a bugzilla instance does exist it is not well maintained or widely used by developers. If you really want to file a bug in bugzilla you are strongly recommended to also post to the mailing list." 
And http://lists.xen.org/archives/html/xen-users/2013-05/msg00556.html says
" it this is an Alpha release and therefore it may be necessary to reset the database to a pristine state before declaring the service production ready."
Therefore, I will consider http://bugs.xenproject.org/xen/ later when it enters later phase.

> 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)

Re: VMX test report for Xen 4.5-unstable-git commit:f7e46156a1c006a6eb5489e0227d39229eec316d

[Ian Campbell]

On Tue, 2014-07-01 at 06:36 +0000, Hu, Robert wrote:
> And http://lists.xen.org/archives/html/xen-users/2013-05/msg00556.html says
> " it this is an Alpha release and therefore it may be necessary to reset the database to a pristine state before declaring the service production ready."
> Therefore, I will consider http://bugs.xenproject.org/xen/ later when it enters later phase.

That email is from a year ago, the bugs.xenproject.org service is no
longer Alpha IMHO (I'm not sure if this was actually announced, I
thought so but I can't find it now). Certainly at this stage I won't be
resetting the database again.

Anyway, the route to filing a bug there is to post to this list and for
the relevant maintainer to decide that it needs recording (as opposed to
e.g. being something which can be taken care of straight away or user
error etc).

The "relevant maintainer" would generally be someone listed in the
MAINTAINERS file, often the maintainer for the bit of code but perhaps
someone else (in recording a bug you are in some sense taking
responsibility for it). As with patches I think it would be a good idea
for you to CC relevant people from the MAINTAINERS file so that they see
it. (I don't think that is necessarily good advice for every end user
wanting to report a bug, but I think for e.g. Intel QA reported bugs it
makes sense).

Information for maintainers on using the bug tracker is at
http://wiki.xen.org/wiki/Xen_Bug_Management_Interface and I'm always
happy to guide etc.

BTW, the bug.xenprojects.org's idea of MAINTAINERS is currently manually
sync'd from the main tree, so it's possible that with turnover of
maintainers it is out of sync. Just shout if this turns out to be the
case.

Ian.