http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1713
Summary: memory corruption was reported by "xl" with device pass-
throu
Product: Xen
Version: unstable
Platform: Other
OS/Version: Windows
Status: NEW
Severity: normal
Priority: P1
Component: Tools
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: shaohui.zheng@intel.com
Environment:
------------
Service Arch (ia32/ia32e/IA64): IA32e
Guest Arch (ia32/ia32e/IA64):
Guest OS Type (Linux/Windows):
Change Set: 22764:75b6287626ee
Hardware:
Other:
pvops dom0: 862ef97190f6b54d35c76c93fb2b8fadd7ab7d68
ioemu : 1c304816043c0ffe14d20d6006d6165cb7fddb9b
Bug detailed description:
--------------------------
Create a HVM guest with any devices pass-throu statically, PCIE NIC or VF.
After We execute comand "xl cr hvm.conf" , xl complains that memory corruption
was detected. If there is no device pass-throu, this warning information will
not appear.
The similar issue also exists when we attach a device dynamically, but it does
not affect the pass-throu feature, Guest OS can use the pass-throu device even
through it complains memory corruption, it is just a warning information.
It might imply some hide issues, so we report it as a P2 bug.
Reproduce steps:
----------------
1. Hide device in HVM config file
pci = [ '05:01.0' ]
2. Create HVM guest with xl command
xl create hvm.conf
You will see this warning information
Current result:
----------------
Warining information for xl create command:
*** glibc detected *** xl: malloc(): memory corruption: 0x000000000162c900 ***
Warining information for xl pci-attach command:
[root@vt-nhm7 ~]# xl pci-attach 2 05:10.1
*** glibc detected *** xl: corrupted double-linked list: 0x0000000001e667d0 ***
Expected result:
----------------
Basic root-causing log:
----------------------
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
Summary: memory corruption was reported by "xl" with device pass-
throu
Product: Xen
Version: unstable
Platform: Other
OS/Version: Windows
Status: NEW
Severity: normal
Priority: P1
Component: Tools
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: shaohui.zheng@intel.com
Environment:
------------
Service Arch (ia32/ia32e/IA64): IA32e
Guest Arch (ia32/ia32e/IA64):
Guest OS Type (Linux/Windows):
Change Set: 22764:75b6287626ee
Hardware:
Other:
pvops dom0: 862ef97190f6b54d35c76c93fb2b8fadd7ab7d68
ioemu : 1c304816043c0ffe14d20d6006d6165cb7fddb9b
Bug detailed description:
--------------------------
Create a HVM guest with any devices pass-throu statically, PCIE NIC or VF.
After We execute comand "xl cr hvm.conf" , xl complains that memory corruption
was detected. If there is no device pass-throu, this warning information will
not appear.
The similar issue also exists when we attach a device dynamically, but it does
not affect the pass-throu feature, Guest OS can use the pass-throu device even
through it complains memory corruption, it is just a warning information.
It might imply some hide issues, so we report it as a P2 bug.
Reproduce steps:
----------------
1. Hide device in HVM config file
pci = [ '05:01.0' ]
2. Create HVM guest with xl command
xl create hvm.conf
You will see this warning information
Current result:
----------------
Warining information for xl create command:
*** glibc detected *** xl: malloc(): memory corruption: 0x000000000162c900 ***
Warining information for xl pci-attach command:
[root@vt-nhm7 ~]# xl pci-attach 2 05:10.1
*** glibc detected *** xl: corrupted double-linked list: 0x0000000001e667d0 ***
Expected result:
----------------
Basic root-causing log:
----------------------
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs