WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1307] New: VT-d NIC does not work in HVM guest

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1307] New: VT-d NIC does not work in HVM guest
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 28 Jul 2008 19:45:57 -0700
Delivery-date: Mon, 28 Jul 2008 19:46:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1307

           Summary: VT-d NIC does not work in HVM guest
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx


Environment:
------------
Service OS (ia32/ia32e/IA64): ia32 ia32e
Guest OS (ia32/ia32e/IA64): ia32 ia32e
Change Set: 18139
Hardware: Stoakley



Bug detailed description:
--------------------------
We create one HVM guest with one PCI or PCIe NIC assigned, the assigned NIC
does not work, guest can not get IP address.

Reproduce steps:
----------------
1) prepare one OS image(linux or Windows)
2) create HVM guest with one NIC assigned


Current result:
----------------


Expected result:
----------------


Basic root-causing log:
----------------------
(XEN) HVM1: unsupported PCI BIOS function 0x0E                                  
(XEN) HVM1: int13_harddisk: function 15, unmapped device for ELDL=81            
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xc0,
me
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xc9,
m5
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xca,
m4
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xcb,
m3
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xcc,
m2
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xcd,
m1
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xce,
m0
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xcf,
mf
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xd0,
me
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xd8,
m6
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xd9,
m5
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xda,
m4
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xdb,
m3
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xdc,
m2
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xdd,
m1
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xde,
m0
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xdf,
mf
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe0,
me
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe1,
md
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe2,
mc
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe3,
mb
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe4,
ma
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe5,
m9
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe6,
m8
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe7,
m7
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe8,
m6
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe9,
m5
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xea,
m4
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xeb,
m3
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xec,
m2
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xed,
m1
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xee,
m0
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xef,
mf
(XEN) hvm.c:1512:d1 guest attempted write to read-only memory page. gfn=0xe0,
me
(XEN) HVM1: *** int 15h function AX=E980, BX=0082 not yet supported!            
(XEN) vlapic.c:601:d1 Notice: Local APIC write with len = 1                     
(XEN) vlapic.c:724:d1 Local APIC Write to read-only register 0x30               
(XEN) common.c:3519:d0 tracking VRAM f0000 - f0026                              
(XEN) irq.c:235: Dom1 PCI link 0 changed 5 -> 0                                 
(XEN) irq.c:235: Dom1 PCI link 1 changed 10 -> 0                                
(XEN) irq.c:235: Dom1 PCI link 2 changed 11 -> 0                                
(XEN) irq.c:235: Dom1 PCI link 3 changed 5 -> 0                                 
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3201 mfn=d8300 nr_mfns=1          
(XEN) domctl.c:857:d0 ioport_map:remove f_gport=c200 f_mport=3000 np=40         
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3000 mfn=d8200 nr_mfns=100        
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3100 mfn=d8100 nr_mfns=100        
(XEN) domctl.c:782:d0 memory_map:add: gfn=f3201 mfn=d8300 nr_mfns=1             
(XEN) domctl.c:833:d0 ioport_map:add f_gport=c200 f_mport=3000 np=40            
(XEN) domctl.c:782:d0 memory_map:add: gfn=f3000 mfn=d8200 nr_mfns=100           
(XEN) domctl.c:782:d0 memory_map:add: gfn=f3100 mfn=d8100 nr_mfns=100           
(XEN) stdvga.c:151:d1 leaving stdvga                                            
(XEN) common.c:3495:d0 stopping tracking VRAM f0000 - f0026                     
(XEN) common.c:3519:d0 tracking VRAM f0000 - f00f0                              
(XEN) common.c:3495:d0 stopping tracking VRAM f0000 - f00f0                     
(XEN) common.c:3519:d0 tracking VRAM f0000 - f00e1                              
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3201 mfn=d8300 nr_mfns=1          
(XEN) domctl.c:857:d0 ioport_map:remove f_gport=c200 f_mport=3000 np=40         
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3000 mfn=d8200 nr_mfns=100        
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3100 mfn=d8100 nr_mfns=100        
(XEN) domctl.c:782:d0 memory_map:add: gfn=f3201 mfn=d8300 nr_mfns=1             
(XEN) domctl.c:833:d0 ioport_map:add f_gport=c200 f_mport=3000 np=40            
(XEN) domctl.c:782:d0 memory_map:add: gfn=f3000 mfn=d8200 nr_mfns=100           
(XEN) domctl.c:782:d0 memory_map:add: gfn=f3100 mfn=d8100 nr_mfns=100           
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3201 mfn=d8300 nr_mfns=1          
(XEN) domctl.c:857:d0 ioport_map:remove f_gport=c200 f_mport=3000 np=40         
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3000 mfn=d8200 nr_mfns=100        
(XEN) domctl.c:792:d0 memory_map:remove: gfn=f3100 mfn=d8100 nr_mfns=100        
(XEN) mm.c:661:d1 Bad L1 flags 10


-- 
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>