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-users

[Xen-users] Re: Xen pci device #0

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: Xen pci device #0
From: Liwei <xieliwei@xxxxxxxxx>
Date: Fri, 1 Jul 2011 23:54:02 +0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Jul 2011 08:55:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OvMKE2hlM2KkXC21T8QC5SUL4Z695gGRpy02PZa+9n4=; b=MMgdPBonxHw/w2Plq9m3H7d9rfL+UymIo4k5PuJcwZhI9X4i3KFMVC/AtjmpepoFNF ZV6jD9GQu3QPIV46e1QTlJvS35v4x4TGdBwN2kGQ8gpnGMV4i8B1QigNkVWDiUBysJQz 3+fO5X7qmkUwyXD4Fjlm2ouS4494tZH2gfohY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01D57F5D@trantor>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTikjQSc00JZoxnBAkqM+0cUR3xXVJg@xxxxxxxxxxxxxx> <BANLkTi=MTEJ33YagzrZ-KVGdYRXwKWGCXw@xxxxxxxxxxxxxx> <BANLkTi=k4tjJ7dqCq3vOmD+6_15giSCGpA@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01D57F35@trantor> <BANLkTikXzMKiHEo+r+4xHsJ+384_ZO9CLg@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01D57F37@trantor> <BANLkTi=FBu2eYrAEzgDvF-Ob3JLXpqskwA@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01D57F39@trantor> <BANLkTim2d-QV4Tv2FRwZc0+Lv=K0RQAu3A@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01D57F3D@trantor> <BANLkTin5FRv-acRNojjcV8JO8WQtccyUcg@xxxxxxxxxxxxxx> <BANLkTikoxS2c_wL-xWBBTUzbrsz5Qos6wA@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01D57F5D@trantor>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 1 July 2011 18:29, James Harper <james.harper@xxxxxxxxxxxxxxxx> wrote:
>
> This doesn't seem to have /PATCHTPR in the boot.ini entry:
>
> 12953982738531: XenPCI     SystemStartOptions = NOEXECUTE=OPTIN
> FASTDETECT
>
> Was it added at the time the log was generated?
>
> James
>

Whoops, forgot that the system restore undid my boot.ini change. See
attached for another log file with patchtpr specified.

Also, to give you a better idea of what I'm seeing, here's the FTP
test result (this is over a 200/100Mb link to my ISP):

========
ISP to VM
(in all instances except for 1meg, the UI becomes unresponsive during
the transfer)
========
ftp> get 1meg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 1meg (1000000 bytes).
226 File send OK.
ftp: 1000000 bytes received in 0.06Seconds 15873.02Kbytes/sec.

ftp> get 5meg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 5meg (5000000 bytes).
226 File send OK.
ftp: 5000000 bytes received in 0.27Seconds 18867.92Kbytes/sec.

ftp> get 10meg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 10meg (10000000 bytes).
226 File send OK.
ftp: 10000000 bytes received in 16.05Seconds 623.17Kbytes/sec.

ftp> get 100meg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 100meg (100000000 bytes).
226 File send OK.
ftp: 100000000 bytes received in 322.48Seconds 310.09Kbytes/sec.

========
VM to ISP
========
ftp> put 1meg
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 1000000 bytes sent in 0.09Seconds 10638.30Kbytes/sec.

ftp> put 5meg
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 5000000 bytes sent in 0.39Seconds 12787.72Kbytes/sec.

ftp> put 10meg
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 10000000 bytes sent in 0.78Seconds 12804.10Kbytes/sec.

ftp> put 100meg
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 100000000 bytes sent in 7.66Seconds 13061.65Kbytes/sec.

Compare the above to what I'm getting from a non-PV VM:

========
ISP to VM
========
ftp> get 1meg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 1meg (1000000 bytes).
226 File send OK.
ftp: 1000000 bytes received in 0.06Seconds 17543.86Kbytes/sec.

ftp> get 5meg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 5meg (5000000 bytes).
226 File send OK.
ftp: 5000000 bytes received in 0.24Seconds 20576.13Kbytes/sec.

ftp> get 10meg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 10meg (10000000 bytes).
226 File send OK.
ftp: 10000000 bytes received in 0.47Seconds 21141.65Kbytes/sec.

ftp> get 50meg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for 50meg (50000000 bytes).
226 File send OK.
ftp: 50000000 bytes received in 2.90Seconds 17241.38Kbytes/sec.

========
VM to ISP
========
ftp> put 1meg
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 1000000 bytes sent in 0.09Seconds 11111.11Kbytes/sec.

ftp> put 5meg
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 5000000 bytes sent in 0.40Seconds 12562.81Kbytes/sec.

ftp> put 10meg
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 10000000 bytes sent in 0.79Seconds 12658.23Kbytes/sec.

ftp> put 50meg
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 50000000 bytes sent in 3.95Seconds 12667.85Kbytes/sec.

Attachment: qemu-dm-XPTest-patchtpr.log
Description: Binary data

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