vmx status report against changeset 15521 - 2 new issues

vmx status report against changeset 15521 - 2 new issues

[Zhao, Yunfeng]

New issues (2)
=================================================
1) Data corrupted after copied into a 32bit win2k3 guest on 64bit
hypervisor with rtl8139
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1025
2) pcnet network of 32bit win2k/64bit hypervisor is not stable.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1026

Fixed issues (1)
=================================================
1. HVM Live migration fails on PAE
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1018
It's a config problem of test machine rather than an issue of xen.

Old issues (3):
=================================================
1).time latency is a negative number on window guest when vcpu > 1
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=895
       You can reproduce it on SMP windows, it will not happen on UP
Windows
2) IA32E/PAE: 32bit Vista RTM network doesn't work.(p1)
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=840
3) PAE dom0  keeps printing "Timer ISR/0: Time went backwards"
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1000


Testing environments 
==============================================
PAE	
CPU		Paxville
Chipset 		Intel Harwich
Dom0 OS			Fedora5
Memory size		8G

IA32e	
Dom0 OS			RHEL4u3
CPU		Woodcrest
Chipset 		Intel 5000(Blackford)
Memory size		12G

Details:
==============================================
PAE:
+ Build&Boot PAE SMP xen0 without problem
+ Can bootup SMP XenU with  256 M Memory
+ Can bootup unmodified RHEL4U1 IA32 nonPAE SMP 2.6 Linux VMX domain
+ Can bootup unmodified RHEL4U1/RHEL4U2/FC5 PAE SMP 2.6 Linux VMX domain
+ Can bootup RHEL4U1/RHEL4U2/FC5 PAE SMP 2.6 Linux VMX domain & XenU
with different memory size
  (VMX:64MB,128MB,196MB,256MB,512MB,1500MB.XenU:256MB)
+ Can bootup RHEL4U1 PAE SMP Linux VMX domain with base kernel
+ xm-test runs well
+ A selected subset of LTP runs well in RHEL4U2 PAE SMP 2.6 Linux VMX
domain 
+ Can build base kenerl 2.6.16 in RHEL4U1 PAE SMP VMX domain.
+ Can startX in Dom0
+ Can bootup FC5 PAE SMP 2.6 Linux in VMX with acpi enable
+ Network is OK in RHEL4U1/RHEL4U2/FC5 PAE SMP VMX domain
+ Can startX in RHEL4U2 PAE SMP VMX domain
+ Can bootup unmodified IA32 UP nonACPI Windows2K VMX domain 
+ Can bootup unmodified IA32 UP ACPI WindowXP SP2 VMX domain
+ Can bootup unmodified PAE UP ACPI Windows2K3 VMX domain 
+ Can bootup unmodified PAE UP ACPI Windows Beta 2 Vista VMX domain 
+ Can bootup unmodified IA32 SMP Win2K3 VMX domain
+ Can bootup unmodified IA32 SMP WinXP VMX domain
+ Can bootup unmodified IA32 SMP Windows Beta 2 Vista VMX domain
+ Can bootup unmodified PAE SMP Windows RTM Vista VMX domains(network
does not work)   
+ VBD and VNIF work on UP and SMP VMX domain can not work
+ Can not save/restore work
+ Can not Live migration

IA32E: 
+ Build&Boot IA32E SMP xen0 without problem
+ Can bootup SMP XenU with  256 M Memory
+ Can bootup unmodified FC5 IA32 nonPAE SMP 2.6 Linux VMX domain
+ Can bootup unmodified FC5 PAE SMP 2.6 Linux VMX domain
+ Can bootup unmodified FC5/RHEL4U1/RHEL4U3 IA32E SMP 2.6 Linux in VMX
+ Can bootup FC5/RHEL4U1/RHEL4U3 IA32E SMP VMX domain & xenU with
different memory size.
  (VMX:128MB,256MB,384MB,512MB,1024M,4096MB.XenU:256MB)
+ Can bootup four FC5 IA32E SMP Linux VMX domain in sequence
+ xm-test runs well
+ A selected subset of LTP runs well in RHEL4U1 IA32E SMP 2.6 Linux VMX
domain 
+ Can build base kenerl 2.6.16 in RHEL4U1 IA32E SMP VMX domain.
+ Can boot up FC3 Linux VMX domain with base kernel
+ Can startX in Dom0
+ Can bootup FC5 IA32E 2.6 Linux VMX domain with acpi enable
+ Can startX in RHEL4U3 Ia32E SMP VMX domain
+ Network is OK in FC5/RHEL4U1/RHEL4U3 IA32E SMP VMX domain
+ Can bootup unmodified IA32 UP ACPI WindowXP SP2 VMX domain
+ Can bootup unmodified IA32 UP ACPI Windows 2K3 VMX domain   
+ Can bootup unmodified IA32 SMP Win2K3 VMX domain
+ Can bootup unmodified IA32 SMP WinXP VMX domain
+ Can bootup unmodified PAE SMP ACPI Windows Beta 2 Vista VMX domain   
+ Can bootup unmodified PAE SMP ACPI Windows RTM Vista VMX
domain(network does not work)   
+ Can bootup unmodified IA32E UP WinXP VMX domain
+ Can bootup unmodified IA32E UP Win2K3 VMX domain
+ Can bootup unmodified IA32E SMP Win2K3 VMX domain
+ Can bootup unmodified IA32E SMP WinXP VMX domain
+ Can bootup unmodified IA32E SMP Windows Beta 2 Vista VMX domain
+ Can bootup unmodified IA32E SMP Windows RTM Vista VMX domain
+ Can bootup >4G IA32E SMP Window RTM Vista VMX domain
+ Can bootup >4G IA32E SMP Linux VMX domain
+ VBD and VNIF work on UP and SMP VMX domain can not work
+ Can not xm save/restore work
+ Can 32-bits PAE xenU boot on 64-bits xen0
+ Can Live migration 

For details
------------------------------------------------------------
Platform: PAE 
Service OS: FC5, PAE, SMP
Hardware: Conroe
Default guest OS: PAE,SMP, 2.6 kernel
 
1, one xenU domain with memory 256M
PASS
2, one IA32 FC5 nonPAE SMP 2.6 VMX domain with memory 256M	PASS
3, one FC5 PAE SMP Linux VMX domain with memory 512M		PASS
4, one FC5 PAE SMP Linux VMX domain with memory 1500M		PASS
5, one RHEL4u1 Linux VMX domain boot with PAE SMP base kernel(2.6.16)
PASS
6, one FC5 PAE SMP Linux VMX domain with acpi enable		PASS
7, 2 FC5 PAE SMP VMX domains and 2 xenU domains coexist		PASS
9, network in xenu domain
PASS
10, network in RHEL4U1/RHEL4U2/FC5 PAE SMP Linux VMX domain	PASS
11, Startx in RHEL4U2 PAE SMP Linux VMX domain			PASS
12, startx in dom0
PASS
13, xm-test
PASS
14, subset LTP test in RHEL4U2 PAE SMP VMX domain
PASS
15, build Linux 2.6.16 base kernel in RHEL4U1 PAE SMP Linux VMX
domainPASS
16, one IA32 nonACPI Window VMX domain 				PASS
17, IA32 UP nonACPI 2K and XPsp2 Windows VMX domains coexist	 PASS
18, one IA32 UP ACPI Windows 2K VMX domain
PASS
19, one IA32 UP ACPI Windows XP sp2 VMX domain			PASS
20, one IA32 UP ACPI Windows 2K3 VMX domain			PASS
21, one IA32 UP ACPI Windows Beta2 Vista VMX domain
PASS
22, one IA32 SMP Windows 2K3 VMX domain				PASS
23, one IA32 SMP Windows XP VMX domain				PASS
24, one IA32 SMP Windows Beta 2 Vista VMX domain
PASS
25, one IA32 SMP Windows RTM Vista VMX domain			PASS
26. VBD and VNIF works on UP VMX domain			PASS
27. Save and Restore
PASS
28. Live migration
PASS

Platform : PAE
Service OS : Fedora Core release 5 (Bordeaux)
Hardware : Conroe
Xen package: 15512:aa640601575f
Date: Tue Jul 10 15:31:45 EDT 2007

               Summary Test Report of Last Session
=====================================================================
  	                    Total   Pass    Fail    NoResult   Crash
=====================================================================
control_panel               12      9       1         2        0
Restart                     1       1       0         0        0
gtest                       14      13      1         0        0
=====================================================================
control_panel               12      9       1         2        0
 :XEN_four_vmx_xenu_seq_P   1       1       0         0        0
 :XEN_4G_guest_PAE_gPAE     1       1       0         0        0
 :XEN_LM_PAE_gPAE           1       0       1         0        0
 :XEN_xenu_pae_on_64_PAE_   1       0       0         1        0
 :XEN_four_dguest_co_PAE_   1       1       0         0        0
 :XEN_linux_win_PAE_gPAE    1       1       0         0        0
 :XEN_SR_PAE_gPAE           1       0       0         1        0
 :XEN_vmx_vcpu_pin_PAE_gP   1       1       0         0        0
 :XEN_1500M_guest_PAE_gPA   1       1       0         0        0
 :XEN_two_winxp_PAE_gPAE    1       1       0         0        0
 :XEN_vmx_4vcpu_PAE_gPAE    1       1       0         0        0
 :XEN_four_sguest_seq_PAE   1       1       0         0        0
Restart                     1       1       0         0        0
 :GuestPAE_PAE_gPAE         1       1       0         0        0
gtest                       14      13      1         0        0
 :boot_up_acpi_PAE_gPAE     1       1       0         0        0
 :ltp_nightly_PAE_gPAE      1       1       0         0        0
 :boot_up_acpi_xp_PAE_gPA   1       1       0         0        0
 :boot_up_vista_PAE_gPAE    1       0       1         0        0
 :boot_up_acpi_win2k3_PAE   1       1       0         0        0
 :boot_base_kernel_PAE_gP   1       1       0         0        0
 :boot_smp_acpi_win2k3_PA   1       1       0         0        0
 :boot_smp_acpi_win2k_PAE   1       1       0         0        0
 :boot_up_acpi_win2k_PAE_   1       1       0         0        0
 :boot_smp_acpi_xp_PAE_gP   1       1       0         0        0
 :boot_up_noacpi_win2k_PA   1       1       0         0        0
 :boot_up_noacpi_win2k3_P   1       1       0         0        0
 :boot_up_noacpi_xp_PAE_g   1       1       0         0        0
 :kb_nightly_PAE_gPAE       1       1       0         0        0
=====================================================================
Total                       27      23      2         2        0
                    
Platform: IA32E
service os: RHEL4u3. IA32E. SMP
hardware: Woodcrest
default guest os: IA32E.SMP. 2.6 kernel

1. one xenU domain with memory 256M
PASS
2. one FC5 IA32 nonPAE SMP 2.6 Linux VMX domain with memory 256M
PASS
3. one FC5 PAE SMP Linux VMX domain with 1500M			PASS
4. one FC5 PAE SMP Linux VMX domain with 5120M memory		PASS
5. one FC5 IA32E SMP Linux VMX domain with 512M memory 		PASS
6. one FC5 IA32E SMP Linux VMX domain with 5120M memory		PASS
7. Two 5120M FC5 IA32E Linux VMX domain coexist			PASS
8. one FC3 Linux VMX boot with IA32E SMP base kernel(2.6.16)
PASS	
9. one FC5 IA32E SMP Linux VMX domain with acpi enable		PASS
10. 2 FC5 IA32E SMP Linux VMX domains and 2 xenU VMX domains coexist
PASS
11. Four FC5 IA32E SMP Linux VMX domains coexist
PASS
12. FC3/FC5/RHEL4u1/RHEL4u3 network in IA32E SMP Linux VMX domain
PASS
13. network in XenU domain
PASS
14. Startx in RHEL4U3 IA32E SMP Linux VMX domain
PASS
15. StartX in Dom0
PASS
16. xm-test
PASS
17. subset LTP in RHEL4U1 IA32E Linux VMX domain
PASS
18. Build base kernel in RHEL4U1 IA32E Linux VMX domain		PASS
19. one IA32 UP nonACPI Windows VMX domain
PASS
20. one IA32 UP noACPI 2K3 and XPsp2 Windows VMX domains coexist PASS
21. one IA32 UP ACPI Windows 2K VMX domain
PASS
22. one IA32 UP ACPI Windows XP VMX domain
PASS
23. one IA32 UP ACPI Windows 2K3 VMX domain			PASS
25. one IA32 SMP Windows XP VMX domain				PASS
26. one IA32 SMP Windows 2K3 VMX domain				PASS
27. one IA32 SMP Windows Beta 2 Vista VMX domain
PASS
28.one IA32 SMP Windows RTM Vista VMX domain			PASS
29. one IA32E UP Windows XP VMX domain				PASS
30. one IA32E UP Windows 2K3 VMX domain				PASS
31. one IA32E UP Windows Vista VMX domain
PASS
32. one IA32E SMP Windows XP VMX domain				PASS
33. one IA32E SMP Windows 2K3 VMX domain
PASS
34. one IA32E SMP Windows Beta 2 Vista VMX domain
PASS
35. one IA32E SMP Windows RTM Vista VMX domain 			PASS
36. one IA32E SMP Windows Vista with 5120 M memory
PASS
37. Two 5120M IA32 SMP Win2K3 VMX domain and
	IA32E Linux VMX domain coexist				PASS
38. VBD and VNIF works on UP VMX domain			PASS
39. Save / Restore
PASS
40. boot 32-bits PAE xenU on 64-bits				PASS 
41. Live migration
PASS

Platform : x86_64
Service OS : Red Hat Enterprise Linux AS release 4 (Nahant Update 3)
Hardware : Woodcrest
Xen package: 15521:1f348e70a5af
Date: Thu Jul 12 15:51:10 CST 2007

               Summary Test Report of Last Session
=====================================================================
  	                    Total   Pass    Fail    NoResult   Crash
=====================================================================
control_panel               16      11      5         0        0
Restart                     2       2       0         0        0
gtest                       13      13      0         0        0
=====================================================================
control_panel               16      11      5         0        0
 :XEN_1500M_guest_64_g64    1       0       1         0        0
 :XEN_256M_xenu_64_gPAE     1       1       0         0        0
 :XEN_vmx_4vcpu_64_g64      1       1       0         0        0
 :XEN_1500M_guest_64_gPAE   1       0       1         0        0
 :XEN_4G_guest_64_gPAE      1       1       0         0        0
 :XEN_SR_64_g64             1       0       1         0        0
 :XEN_four_sguest_seq_64_   1       1       0         0        0
 :XEN_vmx_vcpu_pin_64_g64   1       1       0         0        0
 :XEN_linux_win_64_g64      1       1       0         0        0
 :XEN_LM_64_g64             1       0       1         0        0
 :XEN_two_winxp_64_g64      1       1       0         0        0
 :XEN_four_vmx_xenu_seq_6   1       0       1         0        0
 :XEN_four_sguest_seq_64_   1       1       0         0        0
 :XEN_4G_guest_64_g64       1       1       0         0        0
 :XEN_xenu_pae_on_64_64_g   1       1       0         0        0
 :XEN_four_dguest_co_64_g   1       1       0         0        0
Restart                     2       2       0         0        0
 :GuestPAE_64_gPAE          1       1       0         0        0
 :Guest64_64_gPAE           1       1       0         0        0
gtest                       13      13      0         0        0
 :boot_up_acpi_win2k3_64_   1       1       0         0        0
 :boot_smp_acpi_xp_64_g64   1       1       0         0        0
 :bootx_64_g64              1       1       0         0        0
 :boot_smp_acpi_win2k_64_   1       1       0         0        0
 :boot_up_vista_64_g64      1       1       0         0        0
 :boot_up_noacpi_win2k_64   1       1       0         0        0
 :boot_base_kernel_64_g64   1       1       0         0        0
 :boot_up_acpi_win2k_64_g   1       1       0         0        0
 :boot_up_acpi_xp_64_g64    1       1       0         0        0
 :boot_smp_acpi_win2k3_64   1       1       0         0        0
 :ltp_nightly_64_g64        1       1       0         0        0
 :boot_up_acpi_64_g64       1       1       0         0        0
 :kb_nightly_64_g64         1       1       0         0        0
=====================================================================
Total                       31      26      5         0        0

Yunfeng

Re: vmx status report against changeset 15521 - 2 new issues

[Steven Hand]

>New issues (2)
>=================================================
>1) Data corrupted after copied into a 32bit win2k3 guest on 64bit
>hypervisor with rtl8139
>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1025

Have you tried this with: 
   - 32bit windows guest on 32bit or PAE hypervisor?
   - 64bit windows guest on 64bit hypervisor? 

It'd also be good to know what the extent of the corruption is, e.g. 
if it affects just certain pages, etc.


cheers,

S.

RE: vmx status report against changeset 15521 - 2 new issues

[Zhao, Yunfeng]

>>New issues (2)
>>=================================================
>>1) Data corrupted after copied into a 32bit win2k3 guest on 64bit
>>hypervisor with rtl8139
>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1025
>
>Have you tried this with:
>   - 32bit windows guest on 32bit or PAE hypervisor?
>   - 64bit windows guest on 64bit hypervisor?
[Yunfeng] I tried 32bit/pae and 64bit/64bit, and I cannot reproduce this
issue on them.
>
>It'd also be good to know what the extent of the corruption is, e.g.
>if it affects just certain pages, etc.
[Yunfeng] Do you have any good way to get this kind of info?

>
>
>cheers,
>
>S.

Re: vmx status report against changeset 15521 - 2 new issues

[Steven Hand]

>>>1) Data corrupted after copied into a 32bit win2k3 guest on 64bit
>>>hypervisor with rtl8139
>>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D1025
>>
>>Have you tried this with:
>>   - 32bit windows guest on 32bit or PAE hypervisor?
>>   - 64bit windows guest on 64bit hypervisor?
>[Yunfeng] I tried 32bit/pae and 64bit/64bit, and I cannot reproduce this
>issue on them.

Ok, that's interesting. 

>>It'd also be good to know what the extent of the corruption is, e.g.
>>if it affects just certain pages, etc.
>[Yunfeng] Do you have any good way to get this kind of info?

Just comparing the source and destination file page by page (or byte
by byte) and working out the ranges of differences? 

(To make this even easier, start with a known, homogenous file (e.g. 
all 0xa5 or something) - on receipt check md5sum of each page, and 
note any differences in pages which fail the check). 

cheers,

S.

RE: vmx status report against changeset 15521 - 2 new issues

[Zhao, Yunfeng]

[-- Attachment #1: Type: text/plain, Size: 784 bytes --]


>>>It'd also be good to know what the extent of the corruption is, e.g.
>>>if it affects just certain pages, etc.
>>[Yunfeng] Do you have any good way to get this kind of info?
>
>Just comparing the source and destination file page by page (or byte
>by byte) and working out the ranges of differences?
>
>(To make this even easier, start with a known, homogenous file (e.g.
>all 0xa5 or something) - on receipt check md5sum of each page, and
>note any differences in pages which fail the check).
[Yunfeng] I tried to diff two 400M files that before and after copied
into the guest. The difference is few. But I can not figure out where
the problem is.
I attached the diff. The first half data sect is before copy, and the
second is after copy.

>
>cheers,
>
>S.

[-- Attachment #2: diff.txt --]
[-- Type: text/plain, Size: 3786 bytes --]

20371253,20371288c20371253,20371288
< 136d7340 8e97 5a64 f9bf 444c d62b 24df 9306 a1e6
< 136d7350 2c7a 2f3a 9f98 95c5 7617 c3f8 0873 e86d
< 136d7360 0566 7898 458c 7640 e6cd 8c5f f4fb 908a
< 136d7370 3a3f 7be0 d366 41b7 f1e1 3eb5 9288 34a1
< 136d7380 fff3 87ae cd99 4b5f b2cf 7e03 417f 2389
< 136d7390 0d52 f616 63a0 90f0 2107 59ed e5b1 ac07
< 136d73a0 8666 da59 e1cc e483 e3bc 84d5 ce3f 1865
< 136d73b0 b461 6557 161e 0b5e 84ab 1b92 f41c b68e
< 136d73c0 cf58 3723 4a31 ebdd 31f1 dee0 733b e1c1
< 136d73d0 fe7f 8e11 979d 9eac 56dd a008 1b2b 1de8
< 136d73e0 d3b6 c668 e4d1 550c cf79 8d6a fd18 c97f
< 136d73f0 5a22 b01d 70a3 53d6 1f54 32dc d257 b4fc
< 136d7400 2a18 169c 04e6 6f30 283e cee3 98be 23ec
< 136d7410 be73 1c5b c93e d9a4 a9d3 3c4c d236 19a0
< 136d7420 db06 e1da d8e2 61c8 a2b3 56e7 b77e ecf4
< 136d7430 602f 021a f978 17c1 4d54 c8de fceb 4d0e
< 136d7440 b3ba f254 bdd3 07e3 eeff 87f7 4181 23ba
< 136d7450 f9e8 fb5f 722a 09ab 966b 0a94 53d8 7649
< 136d7460 c7ae 6868 c7c0 5208 b97f 5807 a121 1898
< 136d7470 abd2 0df6 caa7 4e77 06f0 3918 b38a 8256
< 136d7480 e192 cbbe d62d 8c56 5b56 5945 b24d ae71
< 136d7490 dfb1 b8ca 0860 a13a 01b9 0b71 1090 9e56
< 136d74a0 8fc0 b25b 00d8 4da8 1483 9e6f a2bb 3635
< 136d74b0 f4fe 7d6f 5881 4330 2462 70a3 9ab9 3ed2
< 136d74c0 d5ee 8fc5 a701 472a f91d 55b0 009e 96fa
< 136d74d0 1cc5 aa02 60c9 b575 ecae 5177 b659 7a08
< 136d74e0 1432 4be5 5106 718e ae84 638c 8322 9bb0
< 136d74f0 fe9c 4467 a0fb 44d4 b85d 84bc f9a8 094f
< 136d7500 8bc4 43e4 b1e8 35b1 e54b 2b7d e58b 6371
< 136d7510 b3e7 8790 7c0b e0d4 05b1 af53 14f4 35db
< 136d7520 f4e4 6b5e 09cd 9e80 acc0 460c ab97 b077
< 136d7530 ccdc 1eed a40e 2506 c903 c55c 4f96 1ffd
< 136d7540 890f 9cff 6f00 5289 d65c 28b7 3c2f 2275
< 136d7550 4bdd 3b9b 2c4b daf8 f05f 08a5 6c8b 0c4c
< 136d7560 5c01 a23f f00c db6a 5fff 2ca8 a231 4c83
< 136d7570 f911 76f3 f06a a376 7da9 456d a6cb 1291
---
> 136d7340 8e97 0164 ee40 0005 3e16 a453 0076 4311
> 136d7350 40d2 08a8 4500 0500 69dc 4018 3f00 3506
> 136d7360 0acb 30ef c057 9ba8 014a 04bd 6104 45ef
> 136d7370 52a2 7737 50e5 1610 52d0 0075 0000 f000
> 136d7380 ff3b 4d53 2e42 0000 0000 0188 00c8 0100
> 136d7390 f140 0000 3e16 a453 0076 4311 40d2 08a8
> 136d73a0 4500 0000 71df 402b 3f00 3206 0ab5 30ef
> 136d73b0 c057 9ba8 014a 04bd 6204 601b 527c 8337
> 136d73c0 5037 1618 e0d0 007d 9e00 430e 0e4f 1c8b
> 136d73d0 db0d a9a5 40c3 1eca 0756 940f 2f57 ef25
> 136d73e0 017a 63f2 deb2 98f5 acdd 652a 6c66 9c5b
> 136d73f0 852c a84b f2df 1e8f 2ac2 a611 5a79 722f
> 136d7400 000e 574e aeb5 2112 aa23 74b5 052f 118e
> 136d7410 0034 016e cfd9 c86f 7c93 3579 6254 604b
> 136d7420 8050 d622 5a30 084d 50fc 3433 9712 02f7
> 136d7430 8013 5e0b 6127 44db 65a3 eef2 7ab9 9d22
> 136d7440 795a 9c14 3339 fc88 bb39 6abf 1758 5e1a
> 136d7450 6e17 fd5d 0109 8680 64ac 431f 41e0 76b7
> 136d7460 f622 add3 8dba 42ea 7bf3 6903 6860 b689
> 136d7470 889f 4242 5785 e59d e097 27de 5377 bff9
> 136d7480 0000 0000 3d19 012c ee40 0005 3e16 a453
> 136d7490 0076 4311 40d2 08a8 4500 0500 71dc 402c
> 136d74a0 3f00 2d06 0ab7 30ef c057 9ba8 014a 04bd
> 136d74b0 6204 611b 5233 8337 5076 1610 08d0 00a9
> 136d74c0 0000 f000 ff3b 4d53 2e42 0000 0000 0188
> 136d74d0 00c8 0000 0000 0000 0000 0000 0200 ff00
> 136d74e0 00fe c100 0c05 00ff 0000 ffff 0000 0000
> 136d74f0 f000 003b 0000 0000 0000 0000 0000 f000
> 136d7500 1393 6232 9736 553d 782e 98ac 66f7 fc28
> 136d7510 f42d 3801 2d9f c68a 5f10 d041 3f1c 6a45
> 136d7520 8ace e41f fdcf d401 d7ef e334 02a6 ad51
> 136d7530 ecdf 1b79 8cba 3bda 6636 5c67 2c13 2613
> 136d7540 6ed3 a226 3913 2844 0beb 1b0a 7d4b ee24
> 136d7550 e7f8 cb90 d3a6 b7d6 62ba 617a 48ef bf57
> 136d7560 37a9 4aa4 e88b 5ecb 421d e19f 1753 90fb
> 136d7570 828b 2032 f017 a376 7da9 456d a6cb 1291

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: vmx status report against changeset 15521 - 2 new issues

[Mats Petersson]

At 08:31 13/07/2007, Steven Hand wrote:

> >>>1) Data corrupted after copied into a 32bit win2k3 guest on 64bit
> >>>hypervisor with rtl8139
> >>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D1025
> >>
> >>Have you tried this with:
> >>   - 32bit windows guest on 32bit or PAE hypervisor?
> >>   - 64bit windows guest on 64bit hypervisor?
> >[Yunfeng] I tried 32bit/pae and 64bit/64bit, and I cannot reproduce this
> >issue on them.
>
>Ok, that's interesting.
>
> >>It'd also be good to know what the extent of the corruption is, e.g.
> >>if it affects just certain pages, etc.
> >[Yunfeng] Do you have any good way to get this kind of info?
>
>Just comparing the source and destination file page by page (or byte
>by byte) and working out the ranges of differences?


Have you tried filling the buffer in QEMU with a known pattern - from 
the description Steven gave, it looks like it may be using an "old" 
buffer, so after the buffer has been "emptied", could you fill it 
with something, and see if that's what occurs in the "bad packet"? 
[Admittedly, I don't really know if there's any easy way to know when 
the packet has actually been "consumed" by the driver in Windows!).

It also looked like the data in the file was code or something like 
that - have you tried preparing a file where it's easy to see that 
the bytes are in the correct order (e.g. fill a file with longwords 
0, 1, 2, 3, 4, and so on). Then you should be able to see if it's a 
"newer" or "older" packet that is incorrectly inserted (I presume).

--
Mats


>(To make this even easier, start with a known, homogenous file (e.g.
>all 0xa5 or something) - on receipt check md5sum of each page, and
>note any differences in pages which fail the check).
>
>cheers,
>
>S.
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel

RE: vmx status report against changeset 15521 - 2new issues

[Ian Pratt]

> At 08:31 13/07/2007, Steven Hand wrote:
> 
> > >>>1) Data corrupted after copied into a 32bit win2k3 guest on 64bit
> > >>>hypervisor with rtl8139
> > >>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D1025

We fixed this yesterday, and sent the fix upstream to qemu:

http://xenbits.xensource.com/staging/xen-unstable.hg?rev/1158b6115b14

Ian

RE: vmx status report against changeset 15521 - 2new issues

[Zhao, Yunfeng]

Yes, I have tried the patch. With this patch, rtl8139 nic works very well.
Copying big files into a 32bit win2k3 for 10 hours has no any error.

Thanks
Yunfeng

>-----Original Message-----
>From: Ian Pratt [mailto:Ian.Pratt@cl.cam.ac.uk]
>Sent: 2007年7月17日 20:52
>To: Mats Petersson; Steven Hand; Zhao, Yunfeng
>Cc: Steven Hand; xen-devel@lists.xensource.com; Steven.Hand@cl.cam.ac.uk;
>ian.pratt@cl.cam.ac.uk
>Subject: RE: [Xen-devel] vmx status report against changeset 15521 - 2new issues
>
>> At 08:31 13/07/2007, Steven Hand wrote:
>>
>> > >>>1) Data corrupted after copied into a 32bit win2k3 guest on 64bit
>> > >>>hypervisor with rtl8139
>> > >>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D1025
>
>We fixed this yesterday, and sent the fix upstream to qemu:
>
>http://xenbits.xensource.com/staging/xen-unstable.hg?rev/1158b6115b14
>
>Ian