Bug 583913 - DP WLK-Hot-Replace-Device Test and WLK-Hot-Add-Device Test failed in WHQL network testing for Windows2008 x86 and x64
Summary: DP WLK-Hot-Replace-Device Test and WLK-Hot-Add-Device Test failed in WHQL net...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xenpv-win
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 518435 532877 533802
TreeView+ depends on / blocked
 
Reported: 2010-04-20 08:21 UTC by Xiaoli Tian
Modified: 2010-10-07 16:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-11 10:12:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
the failure log of this test job (11.70 KB, text/plain)
2010-04-20 08:21 UTC, Xiaoli Tian
no flags Details

Description Xiaoli Tian 2010-04-20 08:21:11 UTC
Created attachment 407758 [details]
the failure log of this test job

Description of problem:

  DP WLK-Hot-Replace-Device Test and WLK-Hot-Add-Device Test failed in WHQL network testing for Windows2008 x86 and x64:the task "RunJob-check pagefile path" failed,
failures are:1)One instance of the device must not be on the paging path
2)Device instance must have disk storage connected;
more details pls refer to the attached failure log.

Version-Release number of selected component (if applicable):
version of Xen-PV Driver:04/12/2010,1.1.0.3
Kenel is :kernel-xen-2.6.18-195.el5

How reproducible:
always

Steps to Reproduce:
1.prepare the WHQL test environment;
2.start to test DP WLK-Hot-Replace-Device Test -Verify driver support for Hot-Add CPU or DP WLK-Hot-Add-Device Test -Verify driver support for D3 power state
3.
  
Actual results:
failed

Expected results:
pass

Additional info:
the failure log is attached

Comment 1 Paolo Bonzini 2010-04-21 12:46:32 UTC
Can you attach the Xen domain configuration?

Comment 2 Xiaoli Tian 2010-04-22 02:31:44 UTC
(In reply to comment #1)
> Can you attach the Xen domain configuration?    

Hi,Paolo
Configuration of Xen domain is described as following:
(1)Domain0(the host):

 CPU infomation:
 processor       : 15
vendor_id       : GenuineIntel
cpu family      : 6
model           : 26
model name      : Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
stepping        : 5
cpu MHz         : 2261.018
cache size      : 8192 KB
physical id     : 15
siblings        : 1
core id         : 0
cpu cores       : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc ida pni est ssse3 cx16 sse4_1 sse4_2 popcnt lahf_lm
bogomips        : 5655.03
clflush size    : 64
cache_alignment  64
address sizes   : 40 bits physical, 48 bits virtual
power management:

Memory information:
MemTotal:     11943936 kB
MemFree:       8674376 kB
Buffers:        152876 kB
Cached:        2117388 kB
SwapCached:          0 kB
Active:        1441992 kB
Inactive:      1073960 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:     11943936 kB
LowFree:       8674376 kB
SwapTotal:    26738680 kB
SwapFree:     26738680 kB
Dirty:             528 kB
Writeback:           0 kB
AnonPages:      245540 kB
Mapped:          57072 kB
Slab:           119856 kB
PageTables:      25488 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:  32710648 kB
Committed_AS:  1042764 kB

(2)Test domain:
/usr/lib64/xen/bin/qemu-dm -d 5 -m 6144 -boot c -serial pty -vcpus 4 -acpi -usb -k en-us -domain-name Win08_64_Xen
-net nic,vlan=1,macaddr=00:16:36:52:65:cf,model=rtl8139 -net tap,vlan=1,bridge=xenbr1 
-net nic,vlan=2,macaddr=00:16:36:14:15:d7,model=rtl8139 -net tap,vlan=2,bridge=virbr0 
-net nic,vlan=3,macaddr=00:16:36:2b:6f:8f,model=rtl8139 -net tap,vlan=3,bridge=virbr0 
-vnc 127.0.0.1:5 -vncunused
(3)Support domain:
/usr/lib64/xen/bin/qemu-dm -d 2 -m 6144 -boot c -serial pty -vcpus 4 -acpi -usb -k en-us -domain-name Win08_64_Xen_2
-net nic,vlan=1,macaddr=00:16:36:51:60:86,model=rtl8139 -net tap,vlan=1,bridge=virbr0 
-net nic,vlan=2,macaddr=00:16:36:21:dc:54,model=rtl8139 -net tap,vlan=2,bridge=virbr0 
-net nic,vlan=3,macaddr=00:16:36:58:d6:44,model=rtl8139 -net tap,vlan=3,bridge=xenbr1 -vnc 127.0.0.1:2 -vncunused
 
xiaoli

Comment 3 Paolo Bonzini 2010-04-22 07:46:39 UTC
Thanks, can you do an "xm list --long <DOMAIN-ID>" for the domain where you actually ran the test?

Comment 4 Xiaoli Tian 2010-04-22 08:02:57 UTC
(In reply to comment #3)
> Thanks, can you do an "xm list --long <DOMAIN-ID>" for the domain where you
> actually ran the test?    

the output of the above command is :
(domid 5)
    (uuid e6dedb42-7bcb-641f-83f1-1d7cecec4051)
    (vcpus 4)
    (cpu_cap 0)
    (cpu_weight 256.0)
    (memory 6144)
    (shadow_memory 52)
    (maxmem 6144)
    (features )
    (name Win08_64_Xen)
    (on_poweroff destroy)
    (on_reboot restart)
    (on_crash restart)
    (image
        (hvm
            (kernel /usr/lib/xen/boot/hvmloader)
            (vcpus 4)
            (boot c)
            (acpi 1)
            (apic 1)
            (pae 1)
            (usb 1)
            (parallel none)
            (serial pty)
            (device_model /usr/lib64/xen/bin/qemu-dm)
            (vnc 1)
            (vncunused 1)
            (keymap en-us)
        )
    )
    (cpus ())
    (device
        (vif
            (backend 0)
            (script vif-bridge)
            (bridge xenbr1)
            (mac 00:16:36:52:65:cf)
        )
    )
    (device
        (vif
            (backend 0)
            (script vif-bridge)
            (bridge virbr0)
            (mac 00:16:36:14:15:d7)
        )
    )
    (device
        (vif
            (backend 0)
            (script vif-bridge)
            (bridge virbr0)
            (mac 00:16:36:2b:6f:8f)
        )
    )
    (device
        (vbd
            (backend 0)
            (dev hda:disk)
            (uname file:/root/Win2008/Win08-64-NIC.img)
            (mode w)
        )
    )
    (state -b----)
    (shutdown_reason poweroff)
    (cpu_time 583.132852396)
    (online_vcpus 4)
    (up_time 22770.0309548)
    (start_time 1271929136.8)
    (store_mfn 983038)

xiaoli

Comment 5 Paolo Bonzini 2010-05-11 10:12:00 UTC
I think this is due to incorrect setting of EnumerateDevices/EnumerateDevicesOverride, as this works here.

Closing as WORKSFORME for now.


Note You need to log in before you can comment on or make changes to this bug.