VMX status report. Xen:25256 & Dom0:d93dc5c...

VMX status report. Xen:25256 & Dom0:d93dc5c...

[Wu, GabrielX]

Hi all,

This is the test report of xen-unstable tree. There are one bug found.

Version Info:
=================================================================
xen-changeset:   25256
Dom0:          linux.git  3.1.0-rc7 (commit: d93dc5c...) 
=================================================================

New issue(1)
==============
1. cpu weight out of range error when create hvm domU
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1818

Fixed issue(0)
==============

Old issues(8)
==============
1. [ACPI] System cann't resume after do suspend
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
2. [XL]"xl vcpu-set" causes dom0 crash or panic
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
3. [VT-D]fail to detach NIC from guest
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
5. [VT-D] device reset fail when create/destroy guest
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
6. when detaching a VF from hvm guest, "xl dmesg" will show some warning information
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1809
7. RHEL6.2/6.1 guest runs quite slow
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1811
8. after detaching a VF from a guest, shutdown the guest is very slow
  http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812

Thanks,
Wu Ronghui(Gabriel)

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Jan Beulich]

>>> On 04.05.12 at 12:06, "Wu, GabrielX" <gabrielx.wu@intel.com> wrote:
> 6. when detaching a VF from hvm guest, "xl dmesg" will show some warning 
> information
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1809 

Are you sure you still see those messages? Original separate testing
of the patch before it went in confirmed they were gone.

Jan

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Konrad Rzeszutek Wilk]

On Fri, May 04, 2012 at 10:06:26AM +0000, Wu, GabrielX wrote:
> Hi all,
> 
> This is the test report of xen-unstable tree. There are one bug found.
> 
> Version Info:
> =================================================================
> xen-changeset:   25256
> Dom0:          linux.git  3.1.0-rc7 (commit: d93dc5c...) 

Please update your dom0.
> =================================================================
> 
> New issue(1)
> ==============
> 1. cpu weight out of range error when create hvm domU
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1818

And what is the guest config? Does it have any cpu weights?
> 
> Fixed issue(0)
> ==============
> 
> Old issues(8)
> ==============
> 1. [ACPI] System cann't resume after do suspend
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707

That shouldn't be a surprise. The patches for that are not yet
in the mainline.

> 2. [XL]"xl vcpu-set" causes dom0 crash or panic

This should be fixed with 3.4-rc5.

>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> 3. [VT-D]fail to detach NIC from guest

Hmm, the last update is from a year ago. Are you sure this
is an issue?

>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
> 4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747

the bug talks about 2.6.32. Can you update it to include the
3.4 (or 3.3) dmesg output?

> 5. [VT-D] device reset fail when create/destroy guest
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752

Does this happen if you manually echo 1 > ../reset? And is this
an issue with the kernel if you upgrade it to 3.4-rc5?

> 6. when detaching a VF from hvm guest, "xl dmesg" will show some warning information
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1809

.. Not sure about that.

> 7. RHEL6.2/6.1 guest runs quite slow
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1811

Is the issue present when using an LVM disk?

> 8. after detaching a VF from a guest, shutdown the guest is very slow
>   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812

Where does it slow down? When bringing the NIC down or in specific cases?
Is this an issue with if you are using a different guest (say Fedora Core 16?)

> 
> Thanks,
> Wu Ronghui(Gabriel)
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Ren, Yongjie]

> -----Original Message-----
> From: xen-devel-bounces@lists.xen.org
> [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Jan Beulich
> Sent: Friday, May 04, 2012 7:31 PM
> To: Wu, GabrielX
> Cc: xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VMX status report. Xen:25256 & Dom0:d93dc5c...
> 
> >>> On 04.05.12 at 12:06, "Wu, GabrielX" <gabrielx.wu@intel.com>
> wrote:
> > 6. when detaching a VF from hvm guest, "xl dmesg" will show some
> warning
> > information
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1809
> 
> Are you sure you still see those messages? Original separate testing
> of the patch before it went in confirmed they were gone.
> 
Sorry, your patch is already in qemu-xen-unstable tree and the bug has been fixed. 
And, just marked it as verified in the bugzilla.

-Jay

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

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Ren, Yongjie]

> -----Original Message-----
> From: xen-devel-bounces@lists.xen.org
> [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Konrad Rzeszutek
> Wilk
> Sent: Friday, May 04, 2012 9:13 PM
> To: Wu, GabrielX
> Cc: xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VMX status report. Xen:25256 & Dom0:d93dc5c...
> 
> On Fri, May 04, 2012 at 10:06:26AM +0000, Wu, GabrielX wrote:
> > Hi all,
> >
> > This is the test report of xen-unstable tree. There are one bug found.
> >
> > Version Info:
> >
> ============================================================
> =====
> > xen-changeset:   25256
> > Dom0:          linux.git  3.1.0-rc7 (commit: d93dc5c...)
> 
> Please update your dom0.

I think we can use 3.4-RCx kernel as dom0 when sending the report next time.

> >
> ============================================================
> =====
> >
> > New issue(1)
> > ==============
> > 1. cpu weight out of range error when create hvm domU
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1818
> 
> And what is the guest config? Does it have any cpu weights?

Added the config in the BZ.  It doesn't have any cpu weight in config. 
Some other person also reported this issue in the mailing list several days ago.

> >
> > Fixed issue(0)
> > ==============
> >
> > Old issues(8)
> > ==============
> > 1. [ACPI] System cann't resume after do suspend
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> 
> That shouldn't be a surprise. The patches for that are not yet
> in the mainline.
> 
OK. Leave it here as a tracking.

> > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> 
> This should be fixed with 3.4-rc5.
> 
Will update this status in next report based on 3.4-RCx.

> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > 3. [VT-D]fail to detach NIC from guest
> 
> Hmm, the last update is from a year ago. Are you sure this
> is an issue?
> 
Yeah, it still exist.  It may be a similar issue with BZ# 1812.
According to our recent testing, it something about VNC console.
Also added some latest info in the BZ.

> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
> > 4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> 
> the bug talks about 2.6.32. Can you update it to include the
> 3.4 (or 3.3) dmesg output?
> 
This is about 32bit Xen.
As we don't test 32bit Xen for a long time, we may update it when we're free.

> > 5. [VT-D] device reset fail when create/destroy guest
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
> 
> Does this happen if you manually echo 1 > ../reset? And is this
> an issue with the kernel if you upgrade it to 3.4-rc5?
> 
When doing 'echo 1 >../reset', I get the same error as list in the BZ.
"/sys/bus/pci/devices/0000:09:00.0/reset returned -1: Invalid argument".
This bug only exists when we use 'pcistub' to hide a device.
If using 'pciback' to hide the device, it doesn't show any error info.
If Xen will support both 'pcisback' and 'pcistub' to hide a device, I'll leave the bug open in BZ.

> > 6. when detaching a VF from hvm guest, "xl dmesg" will show some
> warning information
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1809
> 
> .. Not sure about that.
> 
Oh, it has been fixed by Jan. Marked as verified.

> > 7. RHEL6.2/6.1 guest runs quite slow
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1811
> 
> Is the issue present when using an LVM disk?
> 
Not sure about this, because we don't use LVM in our testing.
We're still testing this bug. If any update, we'll add it in the BZ.

> > 8. after detaching a VF from a guest, shutdown the guest is very slow
> >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> 
> Where does it slow down? When bringing the NIC down or in specific
> cases?
> Is this an issue with if you are using a different guest (say Fedora Core 16?)
> 
We found it is related to 'stdgva' option in guest config file.
If 'stdvga=1' and 'vnc=1', the guest is not slow when shutdown.
If 'stdvga=0' and 'vnc=1', guest shutdown will be very slow.
Also updated BZ, you can get detailed info in BZ.

> >
> > Thanks,
> > Wu Ronghui(Gabriel)
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Konrad Rzeszutek Wilk]

> > > xen-changeset:   25256
> > > Dom0:          linux.git  3.1.0-rc7 (commit: d93dc5c...)
> > 
> > Please update your dom0.
> 
> I think we can use 3.4-RCx kernel as dom0 when sending the report next time.

Excellent!
> 
> > >
> > ============================================================
> > =====
> > >
> > > New issue(1)
> > > ==============
> > > 1. cpu weight out of range error when create hvm domU
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1818
> > 
> > And what is the guest config? Does it have any cpu weights?
> 
> Added the config in the BZ.  It doesn't have any cpu weight in config. 
> Some other person also reported this issue in the mailing list several days ago.

I think some of the Citrix folks were going to take a look at this.

> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > 3. [VT-D]fail to detach NIC from guest
> > 
> > Hmm, the last update is from a year ago. Are you sure this
> > is an issue?
> > 
> Yeah, it still exist.  It may be a similar issue with BZ# 1812.
> According to our recent testing, it something about VNC console.
> Also added some latest info in the BZ.
> 
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
> > > 4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> > 
> > the bug talks about 2.6.32. Can you update it to include the
> > 3.4 (or 3.3) dmesg output?
> > 
> This is about 32bit Xen.
> As we don't test 32bit Xen for a long time, we may update it when we're free.
> 
> > > 5. [VT-D] device reset fail when create/destroy guest
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
> > 
> > Does this happen if you manually echo 1 > ../reset? And is this
> > an issue with the kernel if you upgrade it to 3.4-rc5?
> > 
> When doing 'echo 1 >../reset', I get the same error as list in the BZ.
> "/sys/bus/pci/devices/0000:09:00.0/reset returned -1: Invalid argument".

OK, so then the device can't do reset's properly. Is this the
physical adaptor or the virtual one?

> This bug only exists when we use 'pcistub' to hide a device.

Ok, so it looks like upstream Linux can't do this properly on that device.

> 
> > > 8. after detaching a VF from a guest, shutdown the guest is very slow
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> > 
> > Where does it slow down? When bringing the NIC down or in specific
> > cases?
> > Is this an issue with if you are using a different guest (say Fedora Core 16?)
> > 
> We found it is related to 'stdgva' option in guest config file.
> If 'stdvga=1' and 'vnc=1', the guest is not slow when shutdown.
> If 'stdvga=0' and 'vnc=1', guest shutdown will be very slow.

What does turning standard VGA and VNC on mean to the guest? Doesn't that mean
that the VGA adapter is gone from the guest? And is this issue only
present if you have PCI devices in the guest? Meaning do you get this
if you boot a normal HVM guest and do 'stdvga=0' and 'vnc='1?

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Pasi Kärkkäinen]

On Thu, May 10, 2012 at 10:38:30AM -0400, Konrad Rzeszutek Wilk wrote:
> > > > xen-changeset:   25256
> > > > Dom0:          linux.git  3.1.0-rc7 (commit: d93dc5c...)
> > > 
> > > Please update your dom0.
> > 
> > I think we can use 3.4-RCx kernel as dom0 when sending the report next time.
> 
> Excellent!
> > 
> > > >
> > > ============================================================
> > > =====
> > > >
> > > > New issue(1)
> > > > ==============
> > > > 1. cpu weight out of range error when create hvm domU
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1818
> > > 
> > > And what is the guest config? Does it have any cpu weights?
> > 
> > Added the config in the BZ.  It doesn't have any cpu weight in config. 
> > Some other person also reported this issue in the mailing list several days ago.
> 
> I think some of the Citrix folks were going to take a look at this.
> 
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > > 3. [VT-D]fail to detach NIC from guest
> > > 
> > > Hmm, the last update is from a year ago. Are you sure this
> > > is an issue?
> > > 
> > Yeah, it still exist.  It may be a similar issue with BZ# 1812.
> > According to our recent testing, it something about VNC console.
> > Also added some latest info in the BZ.
> > 
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
> > > > 4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> > > 
> > > the bug talks about 2.6.32. Can you update it to include the
> > > 3.4 (or 3.3) dmesg output?
> > > 
> > This is about 32bit Xen.
> > As we don't test 32bit Xen for a long time, we may update it when we're free.
> > 
> > > > 5. [VT-D] device reset fail when create/destroy guest
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
> > > 
> > > Does this happen if you manually echo 1 > ../reset? And is this
> > > an issue with the kernel if you upgrade it to 3.4-rc5?
> > > 
> > When doing 'echo 1 >../reset', I get the same error as list in the BZ.
> > "/sys/bus/pci/devices/0000:09:00.0/reset returned -1: Invalid argument".
> 
> OK, so then the device can't do reset's properly. Is this the
> physical adaptor or the virtual one?
> 
> > This bug only exists when we use 'pcistub' to hide a device.
> 
> Ok, so it looks like upstream Linux can't do this properly on that device.
> 
> > 
> > > > 8. after detaching a VF from a guest, shutdown the guest is very slow
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> > > 
> > > Where does it slow down? When bringing the NIC down or in specific
> > > cases?
> > > Is this an issue with if you are using a different guest (say Fedora Core 16?)
> > > 
> > We found it is related to 'stdgva' option in guest config file.
> > If 'stdvga=1' and 'vnc=1', the guest is not slow when shutdown.
> > If 'stdvga=0' and 'vnc=1', guest shutdown will be very slow.
> 
> What does turning standard VGA and VNC on mean to the guest? Doesn't that mean
> that the VGA adapter is gone from the guest? And is this issue only
> present if you have PCI devices in the guest? Meaning do you get this
> if you boot a normal HVM guest and do 'stdvga=0' and 'vnc='1?
> 

stdvga=0 gives you the emulated Cirrus? 

-- Pasi

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Ren, Yongjie]

> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Thursday, May 10, 2012 10:39 PM
> To: Ren, Yongjie
> Cc: Wu, GabrielX; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VMX status report. Xen:25256 & Dom0:d93dc5c...
> 
> > > > xen-changeset:   25256
> > > > Dom0:          linux.git  3.1.0-rc7 (commit: d93dc5c...)
> > >
> > > Please update your dom0.
> >
> > I think we can use 3.4-RCx kernel as dom0 when sending the report next
> time.
> 
> Excellent!
> >
> > > >
> > >
> ============================================================
> > > =====
> > > >
> > > > New issue(1)
> > > > ==============
> > > > 1. cpu weight out of range error when create hvm domU
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1818
> > >
> > > And what is the guest config? Does it have any cpu weights?
> >
> > Added the config in the BZ.  It doesn't have any cpu weight in config.
> > Some other person also reported this issue in the mailing list several days
> ago.
> 
> I think some of the Citrix folks were going to take a look at this.
> 
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > > 3. [VT-D]fail to detach NIC from guest
> > >
> > > Hmm, the last update is from a year ago. Are you sure this
> > > is an issue?
> > >
> > Yeah, it still exist.  It may be a similar issue with BZ# 1812.
> > According to our recent testing, it something about VNC console.
> > Also added some latest info in the BZ.
> >
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
> > > > 4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> > >
> > > the bug talks about 2.6.32. Can you update it to include the
> > > 3.4 (or 3.3) dmesg output?
> > >
> > This is about 32bit Xen.
> > As we don't test 32bit Xen for a long time, we may update it when we're
> free.
> >
> > > > 5. [VT-D] device reset fail when create/destroy guest
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
> > >
> > > Does this happen if you manually echo 1 > ../reset? And is this
> > > an issue with the kernel if you upgrade it to 3.4-rc5?
> > >
> > When doing 'echo 1 >../reset', I get the same error as list in the BZ.
> > "/sys/bus/pci/devices/0000:09:00.0/reset returned -1: Invalid
> argument".
> 
> OK, so then the device can't do reset's properly. Is this the
> physical adaptor or the virtual one?
> 
It's a physical adaptor.

> > This bug only exists when we use 'pcistub' to hide a device.
> 
> Ok, so it looks like upstream Linux can't do this properly on that device.
> 
Yes, I think so. To do some fix on 'pcistub' module might fix this issue.

> >
> > > > 8. after detaching a VF from a guest, shutdown the guest is very slow
> > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> > >
> > > Where does it slow down? When bringing the NIC down or in specific
> > > cases?
> > > Is this an issue with if you are using a different guest (say Fedora Core
> 16?)
> > >
> > We found it is related to 'stdgva' option in guest config file.
> > If 'stdvga=1' and 'vnc=1', the guest is not slow when shutdown.
> > If 'stdvga=0' and 'vnc=1', guest shutdown will be very slow.
> 
> What does turning standard VGA and VNC on mean to the guest? Doesn't
> that mean
> that the VGA adapter is gone from the guest? And is this issue only
> present if you have PCI devices in the guest? Meaning do you get this
> if you boot a normal HVM guest and do 'stdvga=0' and 'vnc='1?

'stdvga=1' will make the guest use a emulated VGA named "Technical Corp. Device 1111".
'stdvga=0' will make the guest use a emulated VGA "Cirrus Logic GD5446".
We found this issue only exist when we shut down the guest in its VNC after we hot remove a PCI device.
As the manual page says, "If your guest supports VBE 2.0 or later (e.g. Windows XP onwards) then you should enable this (stdvga=1)."
I think most of the OS we use today support VBE 2.0 or later. 
And if 'stdvga=1', this issue will not exist.
So, can we set stdvga to TRUE by default in libxl code?

--Jay

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Ren, Yongjie]

> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: Friday, May 11, 2012 12:04 AM
> To: Konrad Rzeszutek Wilk
> Cc: Ren, Yongjie; Wu, GabrielX; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VMX status report. Xen:25256 & Dom0:d93dc5c...
> 
> On Thu, May 10, 2012 at 10:38:30AM -0400, Konrad Rzeszutek Wilk wrote:
> > > > > xen-changeset:   25256
> > > > > Dom0:          linux.git  3.1.0-rc7 (commit: d93dc5c...)
> > > >
> > > > Please update your dom0.
> > >
> > > I think we can use 3.4-RCx kernel as dom0 when sending the report
> next time.
> >
> > Excellent!
> > >
> > > > >
> > > >
> ============================================================
> > > > =====
> > > > >
> > > > > New issue(1)
> > > > > ==============
> > > > > 1. cpu weight out of range error when create hvm domU
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1818
> > > >
> > > > And what is the guest config? Does it have any cpu weights?
> > >
> > > Added the config in the BZ.  It doesn't have any cpu weight in config.
> > > Some other person also reported this issue in the mailing list several
> days ago.
> >
> > I think some of the Citrix folks were going to take a look at this.
> >
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > > > 3. [VT-D]fail to detach NIC from guest
> > > >
> > > > Hmm, the last update is from a year ago. Are you sure this
> > > > is an issue?
> > > >
> > > Yeah, it still exist.  It may be a similar issue with BZ# 1812.
> > > According to our recent testing, it something about VNC console.
> > > Also added some latest info in the BZ.
> > >
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
> > > > > 4. Sometimes Xen panic on ia32pae Sandybridge when restore
> guest
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> > > >
> > > > the bug talks about 2.6.32. Can you update it to include the
> > > > 3.4 (or 3.3) dmesg output?
> > > >
> > > This is about 32bit Xen.
> > > As we don't test 32bit Xen for a long time, we may update it when
> we're free.
> > >
> > > > > 5. [VT-D] device reset fail when create/destroy guest
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
> > > >
> > > > Does this happen if you manually echo 1 > ../reset? And is this
> > > > an issue with the kernel if you upgrade it to 3.4-rc5?
> > > >
> > > When doing 'echo 1 >../reset', I get the same error as list in the BZ.
> > > "/sys/bus/pci/devices/0000:09:00.0/reset returned -1: Invalid
> argument".
> >
> > OK, so then the device can't do reset's properly. Is this the
> > physical adaptor or the virtual one?
> >
> > > This bug only exists when we use 'pcistub' to hide a device.
> >
> > Ok, so it looks like upstream Linux can't do this properly on that device.
> >
> > >
> > > > > 8. after detaching a VF from a guest, shutdown the guest is very
> slow
> > > > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> > > >
> > > > Where does it slow down? When bringing the NIC down or in specific
> > > > cases?
> > > > Is this an issue with if you are using a different guest (say Fedora Core
> 16?)
> > > >
> > > We found it is related to 'stdgva' option in guest config file.
> > > If 'stdvga=1' and 'vnc=1', the guest is not slow when shutdown.
> > > If 'stdvga=0' and 'vnc=1', guest shutdown will be very slow.
> >
> > What does turning standard VGA and VNC on mean to the guest?
> Doesn't that mean
> > that the VGA adapter is gone from the guest? And is this issue only
> > present if you have PCI devices in the guest? Meaning do you get this
> > if you boot a normal HVM guest and do 'stdvga=0' and 'vnc='1?
> >
> 
> stdvga=0 gives you the emulated Cirrus?
> 
Yes, it's Cirrus Logic GD5446 VGA card.

> -- Pasi

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Pasi Kärkkäinen]

On Wed, May 23, 2012 at 01:48:21AM +0000, Ren, Yongjie wrote:
> 
> > > This bug only exists when we use 'pcistub' to hide a device.
> > 
> > Ok, so it looks like upstream Linux can't do this properly on that device.
> > 
> Yes, I think so. To do some fix on 'pcistub' module might fix this issue.
> 

And with xen-pciback it works OK? 

-- Pasi

Re: VMX status report. Xen:25256 & Dom0:d93dc5c...

[Ren, Yongjie]

> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> Sent: Wednesday, May 23, 2012 10:29 PM
> To: Ren, Yongjie
> Cc: Konrad Rzeszutek Wilk; Wu, GabrielX; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VMX status report. Xen:25256 & Dom0:d93dc5c...
> 
> On Wed, May 23, 2012 at 01:48:21AM +0000, Ren, Yongjie wrote:
> >
> > > > This bug only exists when we use 'pcistub' to hide a device.
> > >
> > > Ok, so it looks like upstream Linux can't do this properly on that device.
> > >
> > Yes, I think so. To do some fix on 'pcistub' module might fix this issue.
> >
> 
> And with xen-pciback it works OK?
> 
Yes. We are using xen-pciback recently, and it works fine.
If Xen will not to support 'pci-stub' in future, we can close that bug.